Graphical user interface including dynamic generation of savings option selectors for a financial planning system

ABSTRACT

A graphical user interface for a financial planning system generates and displays a list of savings-option selectors by determining projected retirement incomes for a first savings rate based on an assumed savings type being tax-deferred and non-tax-deferred, and in response to the projected retirement income being higher for the assumed savings type being other than the actual type, including a change-type selector enabling the user to maintain the first savings-rate and update the savings type. The GUI further determines a goal-based savings rate and type that enables the user to meet a user goal, and in response to the goal-based values differing from the actual values, includes a goal-based selector enabling the user to update to the goal-based savings rate and type. The GUI displays the list of savings-option selectors on a savings rate page of the GUI.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/674,407, filed May 21, 2018, and entitled “PLANNING ENGINE FORDYNAMIC ACCOUNT OPTIMIZATION”, which is hereby incorporated by referencein its entirety.

BACKGROUND

The disclosure relates generally to account management, and morespecifically to, a user interface for manipulating account projectionsbased on financial data captured and aggregated from multiple sources.

Increasingly, individuals are responsible for managing their ownpersonal retirement accounts, which may be supplemented by employercontributions. Individual accountholders may be ill-equipped to optimizeretirement accounts, as the lengthy term of the account increasessensitivity to asset allocation, contribution strategies, withdrawstrategies, and changes in supplemental retirement benefits. Forexample, market conditions and/or a projected retirement date mayrequire specific adjustments to the asset allocation of the account.Additionally, contribution and withdrawal policies may change. Forexample, taxes may be adjusted or assessed differently from year toyear. As a result, many participants in financial plans, such asemployer-provided 401(k) plans, would benefit from enrollment in afinancial planning system that provides enhanced service, such asimproved recommendations and visualization tools. However, at least someknown financial planning systems, in attempting to provide a moresophisticated set of tools for the user, present a dramaticallydifferent and/or more complex user interface as compared to the basic401(k) plan management interface to which many users are accustomed. Asa result, many ordinary participants may be dissuaded from enrolling in,or continuing to stay enrolled in, such enhanced services.

Moreover, at least some known conventional on-line financial planningsystems generate a large number of recommendations that overwhelm theordinary user, and/or recommendations that are too complex for theordinary user to grasp, and/or recommendations that result in changesthat appear extreme to the ordinary user. As a result, financialplanning participants using such known systems may be unable orunwilling to take steps to improve their income in retirement.

BRIEF DESCRIPTION

In one aspect, a graphical user interface (GUI) for a financial planningsystem is provided. The financial planning system includes at least oneplanning engine in communication with a database, the database storinguser profiles for a plurality of users, each user registered forservices with respect to a financial account of the respective user.Each of the user profiles includes first values for a user goal field, asavings-rate field, and a savings-type field for the respective user.The GUI includes a savings rate page programmed to generate and displaya list of savings-option selectors by steps of determining, using the atleast one planning engine, a projected retirement income based on afirst value of the savings-rate field and an assumed savings type beingtax-deferred. The steps also include re-determining, using the at leastone planning engine, the projected retirement income based on the firstvalue of the savings-rate field and the assumed savings type beingnon-tax-deferred, and in response to (i) the first value of thesavings-type field being one of tax-deferred and non-tax-deferred, and(ii) the projected retirement income being higher for the assumedsavings type being the other of tax-deferred and non-tax-deferred,including in the list of savings-option selectors a change-type selectorenabling the respective user to (i) maintain the first value of thesavings-rate field and (ii) update the savings-type field to the otherof tax-deferred and non-tax-deferred. The steps further includedetermining, using the at least one planning engine based on the userprofile, a goal-based savings rate and a goal-based savings type,wherein the goal-based savings rate and the goal-based savings type aredetermined based on a minimum savings rate that enables the respectiveuser to meet the first value of the user goal field. In addition, thesteps include, in response to at least one of (i) the goal-based savingsrate differing from the first value of the savings-rate field, and (ii)the goal-based savings type differing from the first value of thesavings-type field, including in the list of savings-option selectors agoal-based selector enabling the respective user to update (i) thesavings-rate field to the goal-based savings rate and (ii) thesavings-type field to the goal-based savings type. The steps alsoinclude displaying the list of savings-option selectors.

In another aspect, a computer-implemented method for implementing agraphical user interface (GUI) for a financial planning system isprovided. The financial planning system includes at least one planningengine in communication with a database, the database storing userprofiles for a plurality of users, each user registered for serviceswith respect to a financial account of the respective user. Each of theuser profiles includes first values for a user goal field, asavings-rate field, and a savings-type field for the respective user.The method includes determining, using the at least one planning engine,a projected retirement income based on a first value of the savings-ratefield and an assumed savings type being tax-deferred. The method alsoincludes re-determining, using the at least one planning engine, theprojected retirement income based on the first value of the savings-ratefield and the assumed savings type being non-tax-deferred, and inresponse to (i) the first value of the savings-type field being one oftax-deferred and non-tax-deferred, and (ii) the projected retirementincome being higher for the assumed savings type being the other oftax-deferred and non-tax-deferred, including in the list ofsavings-option selectors a change-type selector enabling the respectiveuser to (i) maintain the first value of the savings-rate field and (ii)update the savings-type field to the other of tax-deferred andnon-tax-deferred. The method further includes determining, using the atleast one planning engine based on the user profile, a goal-basedsavings rate and a goal-based savings type, wherein the goal-basedsavings rate and the goal-based savings type are determined based on aminimum savings rate that enables the respective user to meet the firstvalue of the user goal field. In addition, the method includes, inresponse to at least one of (i) the goal-based savings rate differingfrom the first value of the savings-rate field, and (ii) the goal-basedsavings type differing from the first value of the savings-type field,including in the list of savings-option selectors a goal-based selectorenabling the respective user to update (i) the savings-rate field to thegoal-based savings rate and (ii) the savings-type field to thegoal-based savings type. The method also includes displaying the list ofsavings-option selectors on a savings rate page of the GUI.

In another aspect, at least one non-transitory computer-readable storagemedia that includes computer-executable instructions for implementing agraphical user interface (GUI) for a financial planning system isprovided. The financial planning system includes at least one planningengine in communication with a database, the database storing userprofiles for a plurality of users, each user registered for serviceswith respect to a financial account of the respective user. Each of theuser profiles includes first values for a user goal field, asavings-rate field, and a savings-type field for the respective user.The GUI is generated by at least one processor, wherein when executed bythe at least one processor, the computer-executable instructions causethe at least one processor to determine, using the at least one planningengine, a projected retirement income based on a first value of thesavings-rate field and an assumed savings type being tax-deferred. Thecomputer-executable instructions also cause the at least one processorto re-determine, using the at least one planning engine, the projectedretirement income based on the first value of the savings-rate field andthe assumed savings type being non-tax-deferred, and in response to (i)the first value of the savings-type field being one of tax-deferred andnon-tax-deferred, and (ii) the projected retirement income being higherfor the assumed savings type being the other of tax-deferred andnon-tax-deferred, include in the list of savings-option selectors achange-type selector enabling the respective user to (i) maintain thefirst value of the savings-rate field and (ii) update the savings-typefield to the other of tax-deferred and non-tax-deferred. Thecomputer-executable instructions further cause the at least oneprocessor to determine, using the at least one planning engine based onthe user profile, a goal-based savings rate and a goal-based savingstype, wherein the goal-based savings rate and the goal-based savingstype are determined based on a minimum savings rate that enables therespective user to meet the first value of the user goal field. Inaddition, the computer-executable instructions cause the at least oneprocessor to, in response to at least one of (i) the goal-based savingsrate differing from the first value of the savings-rate field, and (ii)the goal-based savings type differing from the first value of thesavings-type field, include in the list of savings-option selectors agoal-based selector enabling the respective user to update (i) thesavings-rate field to the goal-based savings rate and (ii) thesavings-type field to the goal-based savings type. Thecomputer-executable instructions also cause the at least one processorto display the list of savings-option selectors on a savings rate pageof the GUI.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-57 show example embodiments of the methods and systems describedherein.

FIG. 1 is a simplified block diagram of an example financial planning(FP) system.

FIG. 2 is a component diagram illustrating components of the financialplanning system shown in FIG. 1A.

FIG. 3 illustrates an exemplary interface outline for a graphical userinterface (GUI).

FIG. 4 depicts an example introductory page, such as introductory pageof GUI shown in FIG. 3, which is generated and transmitted by planningengine.

FIG. 5 depicts an example homepage, such as Home page, which is causesto be displayed as the introductory page by GUI for a user enrolled inthe enhanced level service (e.g., after becoming an enhanced-leveluser).

FIG. 6 depicts goals configuration display of GUI, which allows a userto change (e.g., edit) values for certain data fields in database, whichare to be used as inputs used by planning engine to generate financialprojections.

FIG. 7 depicts goals configuration display having second member tabselected.

FIG. 8A depicts an exemplary informational page of GUI which provides auser with a tabular comparison of services available through thefinancial planning system.

FIG. 8B depicts an exemplary informational sub-page of GUI whichprovides a user with more information about the financial advisorysystem driven by planning engine.

FIG. 8C depicts another exemplary informational page of GUI whichprovides a user with a comparison of services available through thefinancial planning system.

FIG. 9 depicts registration page of GUI. Registration page allows a userto register for the financial advisory system and input relevantpersonal and financial information.

FIG. 10 depicts enrollment confirmation page of GUI.

FIG. 11 depicts an exemplary dashboard of GUI, such as dashboard,provided for enhanced-level users.

FIG. 12 depicts an exemplary about me page (or “user profile page”) ofGUI, such as about me page, which may be opened using about me link.

FIG. 13 depicts an exemplary spouse status page of GUI, which may beopened via about me link, and facilitates user selecting if they have aspouse or partner.

FIG. 14 depicts the exemplary spouse status page with a spouse detailregion.

FIG. 15 depicts an exemplary dependent status page.

FIG. 16 depicts the dependent status page with a dependent detailregion.

FIG. 17 depicts an exemplary asset status page.

FIG. 18 depicts an exemplary supplemental income page.

FIG. 19 depicts an exemplary supplemental income detail page.

FIG. 20 depicts an exemplary supplemental income summary region as apart of the supplemental income page.

FIG. 21 illustrates savings goals page of GUI, which may be opened usingsavings goals link and is configured to allow user to add additionalsavings goals which may or may not be related to retirement.

FIG. 22 illustrates savings goals summary page of GUI, which isconfigured to display a summary of savings goals input by user inresponse to selection of save button.

FIG. 23 depicts investments page of GUI, which may be opened usinginvestments link (shown in FIG. 11) and displays graphical and numericdescriptions of the composition of the user's financial account.

FIG. 24 depicts an exemplary asset class composition within theinvestments page.

FIG. 25 depicts an exemplary fund composition within the investmentspage.

FIG. 26 depicts an exemplary constraints page for updating preferredconstraints used by planning engine for determining financialprojections.

FIG. 27 depicts an exemplary strategy selection options and strategyselection indicators within the constraints page.

FIG. 28 depicts an exemplary strategy change summary page of GUI fordisplaying a summary of changes made to a user's investment strategy inresponse to selection of save preferences button.

FIG. 29 depicts an exemplary update to investments page of GUI (shown inFIGS. 23-25) in response to selection of one or more strategy selectionoptions.

FIG. 30A depicts retirement summary page of GUI, which may be openedusing income planning link and displays projected replacement incomecompared to a retirement goal.

FIG. 30B illustrates another example projected retirement income graphsimilar to graph.

FIG. 31 depicts a current plan tab of retirement summary page enlargedto show an income detail region in response to user selecting aretirement year on retirement summary page.

FIG. 32 depicts plan model tab selected on retirement summary page.

FIG. 33 depicts revisiting goals page, which facilitates user defining amodel retirement goal for comparison purposes, by providing financialdata such as model replacement income percentage, model retirement age,model social security age, and model life expectancy.

FIG. 34 depicts updated plan model tab.

FIG. 35 depicts an exemplary savings rate page of GUI, which may beopened using savings link, and facilitates user input of account data,such as a desired contribution rate, and displays a plurality ofcontribution rate levels.

FIG. 36 illustrates slider moved to a new location, which, in theexample embodiment, increases the contribution rate to 5%.

FIG. 37 depicts an exemplary savings type page of GUI, which may openautomatically in response to selecting a savings contribution usingsavings rate page.

FIG. 38 depicts savings type page enlarged to include an exemplarymanual selector region in response to selection of manual contributiontype.

FIG. 39 depicts an exemplary contribution review page of GUI, whichdisplays a summary of changes made to a user's contribution preferencesvia pages and and receives user input confirming the changes from asubmit changes button.

FIG. 40 depicts an exemplary contribution confirmation page of GUI,which displays a confirmation notice of changes made to a user'scontribution preferences in response to selection of submit changesbutton.

FIG. 41 depicts an exemplary savings goal page of GUI, which may beopened using retirement goal link, and which displays financialinformation related to a user's financial goals.

FIG. 42 depicts an alternative exemplary embodiment of savings ratepage, here designated savings rate page.

FIG. 43 depicts an exemplary investment advice page that may be provideas a part of the online advice services to the user.

FIG. 44 depicts an exemplary change review page. If the user chooses tocontinue with the recommended allocations, the opportunity rules enginedisplays the change review page to the user.

FIG. 45 depicts an exemplary confirmation page.

FIG. 46 depicts an exemplary social security page that allows the userto identify at what age they intent to begin taking Social Securitybenefit.

FIG. 47 depicts an exemplary social security benefits page thatillustrates social security benefits calculations for the user based onretirement age.

FIG. 48 depicts an exemplary institution selection page that allows theuser to identify a third-party institution which may manage investmentsof the user.

FIG. 49 depicts an exemplary account link page that allows the user toidentify information about a linked account.

FIG. 50 depicts an exemplary retirement asset page that allows the userto add a retirement asset to their portfolio.

FIGS. 51A and 51B depict exemplary asset configuration pages that allowsthe user to configure assets.

FIGS. 52A and 52B depict exemplary account configuration pages thatallows the user to configure accounts.

FIGS. 53A and 53B depict exemplary account configuration pages thatallows the user to configure accounts.

FIG. 54 is an exemplary assets page that allows the user to add and viewtheir accounts.

FIG. 55 is an exemplary savings goals page that allows the user to addsavings goals.

FIG. 56 is an exemplary add retirement asset page that allows the userto add a retirement asset.

FIG. 57 is an exemplary opportunities page that allows the user to viewand step through opportunities, as discussed above.

DETAILED DESCRIPTION

The following detailed description illustrates embodiments of thedisclosure by way of example and not by way of limitation. Thedescription enables one skilled in the art to make and use thedisclosure. It also describes several embodiments, adaptations,variations, alternatives, and uses of the disclosure, including what ispresently believed to be the best mode of carrying out the disclosure.

The systems and methods of the disclosure facilitate generating accountprojections based on financial data captured and aggregated frommultiple sources, and alerting accountholders in response to changes inthe account projection.

A GUI computer system for providing a graphical user interface (GUI) isprovided. The GUI computer system is in communication with at least oneplanning engine. The planning engine includes multiple optimizationmodules for planning significant personal economic events (e.g.,investment, savings, retirement). The GUI computer system is configuredto capture and centrally store user profile data, including thefinancial data used by the optimization modules, such as the compositionof investment accounts (e.g., employer-provided 401(k) plans). Theplanning engine is configured to retrieve additional financial data frommultiple external data sources, such as asset return projections.Additionally, the GUI computer system may be configured to provide a webinterface to capture financial data from the user. For example, the GUIcomputer system may provide a HTTP API or an interactive web applicationthrough which the user can enter data. Additionally, the GUI computersystem may be configured to cause the GUI to be displayed by anapplication installed on a mobile device of a user.

The planning engine is configured to generate account projections inresponse to captured financial data. In some embodiments, the planningengine generates account projections (e.g., in near-real-time) based onupdated financial data retrieved from the external data sources (e.g.,third-party banking institutions, investment institutions) and/or fromthe user interface. For example, a deferral optimization modulegenerates an updated account projection based on changes in employercontribution formulas, maximum contribution formulas, effective taxrates, current contribution rates, account allocation, project returndata, and the like.

In certain embodiments, the GUI computer system provides basic orintroductory-level services for an existing retirement account. Forexample, the retirement account is associated with a 401(k) or similarplan provided by an employer, and the GUI computer system provides adefault user interface to employees to allow each employee to monitorperformance and/or update basic data regarding the account. In addition,the GUI computer system provides an option to register for enhancedservices, such as a financial advisor program that integrates otheraccounts and benefits of the user into a unified retirement incomeanalysis and planning system. For users who register for the enhancedservices, the GUI computer system maintains and builds upon thegraphical GUI associated with the introductory-level services, addingadditional functionality and features in order to provide a familiar andstreamlined user experience to users who register, thus reducingbarriers to user enrollment for the enhanced service level. In some suchembodiments, the planning engine includes a first planning engineconfigured to receive calls from the GUI and provide financialprojections for the basic or default service level, and a secondplanning engine configured to receive calls from the GUI and providefinancial projections and recommendations for the enhanced servicelevel. Alternatively, a single planning engine interfaces with the GUIfor both service levels.

In some embodiments, the GUI computer system is configured to generatealerts based on the updated account projection. In some embodiments,where the GUI computer system is configured to compare accountprojections with stored financial goals, the GUI computer system may beconfigured to alert accountholders when an account projection does notsatisfy a stored financial goal. Additionally, the GUI computer systemmay be configured to call the planning engine to generate an updatedaccount configuration (e.g., contribution amount, asset allocation) inresponse to the updated account projection.

As such, the GUI computer system allows the user to receive benefits inmanaging a retirement plan by, for example, projecting investmentaccount balances, estimating investment income, evaluating the effect ofplanned contributions, evaluating the effect of benefit plans, adjustingaccount asset compositions, projecting required replacement income, anddetermining a withdrawal schedule. Collection, analysis, and targetedpresentation of such user and market data allows the user to betterdetermine whether they are on target to meet their retirement goals ormanage their wealth during retirement.

FIG. 1 is a simplified block diagram of an example financial planning(FP) system 100 used for generating account projections based onfinancial data captured from multiple sources, and alertingaccountholders in response to changes in the account projection. In anexample embodiment, FP system 100 includes GUI computer system 114, forexample implemented on a server computing device, configured tointerface with at least one planning engine 150. Planning engine 150includes projection and optimization modules 152, which are configuredto perform various analytical tasks with regard to analyzing aretirement portfolio of a user 102. The optimization modules aredescribed in greater detail below with respect to FIG. 2.

In the example embodiment, FP system 100 also includes at least one usercomputing device 112. In some embodiments, user computing device 112includes computing devices configured to implement a web browser or asoftware application, which enables user computing device 112 tocommunicate with server GUI computer system 114 (e.g., using theInternet.) User computing device 112 and GUI computer system 114 may becommunicatively coupled through various networks or network interfacesincluding, but not limited to, at least one of a network, such as theInternet, a local area network (LAN), a wide area network (WAN), anintegrated services digital network (ISDN), a dial-up-connection, adigital subscriber line (DSL), a cellular phone connection, and a cablemodem. Alternatively, user computing device 112/or and GUI computersystem 114 include any device capable of accessing the Internet such as,for example, a desktop computer, a laptop computer, a personal digitalassistant (PDA), a cellular phone, a smartphone, a tablet, a phablet, orother web-based connectable equipment. User computing device 112 may becomputing devices associated with at least one user 102, and may becommunicatively coupled to GUI computer system 114.

In one embodiment, GUI computer system 114 includes a database server118 that is communicatively coupled to a database 120. Database 120stores user profile data associated with a plurality of users 102,account data associated with users 102, financial projections generatedby the optimization modules, and other data that may be required forplanning engine 150 to function as described herein. GUI computer system114 is configured to centrally store account data, asset data, userprofile data, and asset class data in database 120. GUI computer system114 uses database server 118 to interface with database 120.

According to the example embodiment, database 120 is disposed remotelyfrom GUI computer system 114. In other embodiments, database 120 iscentralized, and may be a part of GUI computer system 114. In theexample embodiment, an administrator or a financial planner (not shown)associated with FP system 100 or user 102 is able to access database 120through a user computing device, such as user computing device 112, bylogging onto GUI computer system 114. In the example embodiment, GUIcomputer system 114 may be associated with a financial services provideror financial account recordkeeper (not shown).

GUI computer system 114 is configured to capture and centrally storefinancial data associated with a financial portfolio of the user 102. Insome embodiments, GUI computer system 114 provides an interactive webapplication to user computing device 112, through which the user 102 canenter data or otherwise interact with GUI computer system 114.Additionally, GUI computer system 114 may provide an API (e.g., a HTTPAPI), through which financial data may be received from one or morefinancial data sources 116. Financial data received from financial datasources 116 may include, for example, interest rates, projected growthrates for various funds or asset classes, the compositions of fundsmanaged by third parties, and/or employer contribution data. GUIcomputer system 114 may use database server 118 to store receivedfinancial data in database 120. For example, database server 118 mayparse financial data received from user computing device 112, planningengine 150, and/or financial data sources 116 before storing thefinancial data in database 120.

In the example embodiment, web server 154 generates and transmits webpages to user computing device 112 to implement the GUI. The generatedweb pages may be configured to capture data from user 102, and transmitit back to server computing device 114. For example, user 102 may fillform fields on a webpage. Additionally, web server 154 may generatevisualizations and/or representations of data (e.g., account balanceprojections) for display on user computing device 112 (e.g. on aretirement planning dashboard).

FIG. 2 is a component diagram illustrating components of the at leastone planning engine 150 shown in FIG. 1. In the example embodiment,planning engine 150 generates an extended term financial projectionbased on user profile data (e.g., financial goals, age, projectedretirement date) and account data (e.g., asset data, contribution data,benefit data, income data) to help user 102 plan for retirement.Planning engine 150 includes advisory rules engine 202, returncalculation module 204, investment income module 206, contributionsmodule 208, benefits module 210, replacement income module 212, anddistributions module 214. Modules 204, 206, 208, 210, 212, and 214 maybe examples of projection and optimization modules 152 (shown in FIG.1A).

Advisory rules engine 202 is configured to execute and scheduleoptimization modules based on user profile data and account dataretrieved from GUI computer system 114. Advisory rules engine 202manages operation of: (i) return calculation module 204 (e.g. to projectaccount balances over time based on asset data), (ii) contributionsmodule 208 (e.g. to adjust account balances generated by returncalculation module 204 based on planned asset contribution data), (iii)benefits module 210 (e.g. to project the value of benefit plans), (iv)investment income module 206 (e.g. to project investment income based onaccount balances generated by return calculation module 204), (v)replacement income module 212 (e.g. to determine a replacement incomeamount based on user profile data), and (vi) distributions module 214(e.g. to generate distribution schedules based on the investment incomedata generated by investment income module 206).

Return calculation module 204 is configured to receive account dataincluding asset identifiers from GUI computer system 114, to calculatean expected return and standard deviation for each asset, and to derivean overall expected return and account standard deviation using theresults for each of the assets. For example, an account may includeassets of multiple types, such as securities, electronically tradedfunds, managed funds, bonds, and the like. Return calculation modules204 applies any suitable algorithm to calculate the expected return andstandard deviation for each type of asset.

In some embodiments, for each asset identifier, return calculationmodule 204 is configured to determine if the asset is managed ornon-managed. In response to each asset identifier determined to benon-managed, return calculation module 204 determines the composition ofthe asset. In the example embodiment, return calculation module 204determines asset class composition percentages. For example, returncalculation module 204 may determine an asset is composed of 40%technology stock, and 60% municipal bonds. Return calculation module 204retrieves expected return, standard deviation, and covariance data foreach asset class. For example, technology stocks may have an expectedreturn of 10% with a standard deviation of 0.4.

In response to each asset identifier determined to be managed, aglidepath module may be called. Alternatively, return calculation module204 calculates expected returns in any suitable fashion. For example,return calculation module 204 generates projected account balance databased on expected return, standard deviation, and covariance dataretrieved for each asset. More specifically, return calculation module204 generates an account expected return based on aggregating theexpected return of each asset. Additionally, return calculation module204 generates an account standard deviation based on aggregating theretrieved standard deviation data for each asset.

Return calculation module 204 outputs a matrix of account expectedreturns, including the account expected return, and account expectedreturns modified by the aggregated standard deviation data. For example,account balances at multiples of the standard deviation may be output.In some embodiments, return calculation module 204 is configured toreturn the expected return matrix to GUI computer system 114, to bestored in database 120 using the account identifier.

Additionally, return calculation module 204 is configured to generate aprojected account balance using the expected return matrix. Returncalculation module 204 receives a baseline account balance, such as aprevious year account balance or current account balance. The previousyear account balance may be zero. Return calculation module 204iteratively applies the expected return matrix to the baseline accountbalance to generate an account balance projection. In the exampleembodiment, return calculation module 204 determines projected annualbalances. For example, annual account balances may be projected for aterm of 50 years. In some embodiments, the account balance projectionterm may be received from GUI computer system 114, where database 120stores a financial goal (e.g., retirement date, savings goal). Forexample, return calculation module 204 may project annual accountbalances until a projected retirement date based on the expected returnmatrix.

In the example embodiment, investment income module 206 determines aspending rate based on projected account balances generated by returncalculation module 204. The spending rate may define monthly investmentincome during retirement. For example, investment income module 206 maydetermine an account valued at $130,000 will generate $3,200 inestimated monthly retirement income. Investment income module 206searches through spending rates to find a desired spending rate. Inother words, investment income module 206 may calculate the effect ofvarious spending rates, and select a spending rate such that the accountbalance is not exhausted during a time period such as a period ofretirement or disability. Additionally, investment income module 206 maygenerate adjusted spending rates using the expected return matrix (e.g.,standard deviation data) generated by return calculation module 204.Investment income module 206 may generate multiple spending ratesassociated with above and below average performance, as defined by thestandard deviation data.

In some embodiments, investment income module 206 determines a projectedlife expectancy of user 102. For example, investment income module 206may determine an expected retirement term. In combination with userprofile data (e.g., demographic data, retirement data), investmentincome module 206 may project the number of years in which retirementinvestment income may be needed. In some examples, investment incomemodule 206 may utilize mortality weighting to estimate life expectancyof user 102. In other examples, investment income module 206 mayestimate life expectancies based on demographic data such as healthstates, age, and sex of users. As another example, investment incomemodule 206 may determine an expected disability term (e.g. a number ofyears where investment income is needed to offset disability supportexpenses).

Contributions module 208 is configured to adjust account balancesgenerated by return calculation module 204 based on planned assetcontribution data. For example, a portion of salary income of user 102may be contributed to the account until retirement (e.g. on a monthlybasis), which may also be supplemented by an employer (e.g. as apercentage matching contribution up to a predetermined limit). Asanother example, a specific dollar amount may be contributed on anannual basis (e.g. by user 102 or by user 102's employer).

For salary contributions, contributions module 208 adjusts the projectedaccount balances generated by return calculation module 204. Morespecifically, each annual account balance projection is increased by thecorresponding projected salary contribution. Further, subsequent yearssalary contributions may be adjusted based on projected salary growth.For example, contributions module 208 may identify an initial accountbalance of $100,000 and an initial salary of $50,000, and may determinethat a 5% contribution in the first year results in a year-end accountbalance of $102,500. In the subsequent year, contributions module 208projects may project that the salary of user 102 will grow to $55,000,and, as such, the subsequent year's contribution will be $2,750.

To project salary growth, contributions module 208 receives salary andemployment data (e.g., job title, profession, career field, employeridentifier) from GUI computer system 114 and estimates a salary growthrate based on the employment data. For example, contributions module 208may determine a salary growth rate of 5% for an accountant, and a salarygrowth rate of 4% for an engineer.

Contributions module 208 may further calculate an employer contribution.Certain employers may match employee contributions or may provide apredetermined amount, such as a fixed amount or a fixed percentage ofuser 102's salary. Contributions may be matched at varying rates, andmay be limited by the employer. Contributions module 208 may receiveemployer contribution data (e.g. a match rate and a match limit) andadjust salary contributions based on the employer contribution data.Salary contributions may be adjusted by both projected salary growth andemployer matching. For example, an employer may match 50% of anemployee's contributions, up to a limit of $10,000 or 10% of theemployee's salary, whichever is lower. For a salary of $50,000, and anemployee contribution rate of 5%, the employer may match $1,250. Asanother example, with a salary of $200,000 and an employee contributionof 10%, the employer may match $10,000. As such, the employer mayrepresent an example financial data source 116.

Additionally, contributions module 208 is configured to determine thepost-tax amount of contributions, where applicable. Contributions module208 may identify an effective tax rate (e.g. based on the salary data)and project a net contribution. For example, $2,500 may be contributedto a taxable account. Contributions module 208 determines the effectivetax rate for the user is 15%, and adjusts the account balance by $2,125.

Contributions module 208 is further configured to compare calculatedcontributions to account-specific limits. Certain accounts may havepre-tax or post-tax contribution restrictions. For example, post-taxretirement accounts may be limited to $18,000 of contributions per year.GUI computer system 114 determines when contributions are projected toexceed the limit, and may cap the contribution amount based on thelimit. In some embodiments, GUI computer system 114 alerts user 102, viaGUI 301, that a contribution limit has been or will be reached. In otherembodiments, GUI computer system 114 reallocates the contributionsbetween restricted accounts (e.g., post-tax retirement account) andother accounts (e.g., health savings account, taxed account).

Contributions module 208 may also adjust projected account balancesbased on dollar amount contributions. For example, user 102 maycontribute exactly $5,000 annually (e.g. in lieu of or in addition toany salary-based contributions). Contributions module 208 may accountfor direct contributions in addition to projected salary contributions.

Benefits module 210 is configured to consider the value of variousbenefit plans (e.g., social security payments, pension plans, insuranceplans) based on information received from GUI computer system 114. Forexample, investment income and social security income may be availableto user 102 during retirement. Further, user 102 may have specializedpension plans (e.g., defined benefit plans, defined contribution plans)or annuities.

GUI computer system 114 is configured to project social security income.In the example embodiment, social security income is projected byretrieving a social security benefit model from database 120, and userprofile data (e.g., salary data, retirement data) from database 120. Insome embodiments, GUI computer system 114 may adjust social securitybased on spousal social security income. More specifically, GUI computersystem 114 may retrieve the user profile of a spouse, and determine ifsocial security income should be projected based on a spousal benefit,or the combination of individual earnings-based benefits. In otherwords, benefits module 210 may receive a spouse profile (e.g., salarydata, citizenship data, and retirement data) and determine if the 50%spousal benefit should be claimed instead of the earnings-based spousalbenefit.

Benefits module 210 is further configured to project the incomegenerated by pension plans, defined benefit plans, defined contributionplans, insurance policies, and annuities. In some embodiments, benefitsmodule 210 receives user-input benefit data, such as start years, endyears, and amounts. Additionally, benefits module 210 may retrieveincome data associated with a user-input benefit from one of financialdata sources 116. For example, benefits module 210 may query theprovider of an employer pension plan to determine a projected pensionincome. Similarly, benefits module 210 may project the cash flow ofinsurance policies and annuities. In certain embodiments, benefitsmodule 210 may be further configured to adjust benefit income based onprojected inflation. More specifically, benefits module 210 may apply aninflation rate to a benefit value.

Replacement income module 212 is configured to receive a replacementincome amount based on user profile data (e.g., income data, incomeprojection data). Replacement income module 212 is configured toestimate expenses in retirement, also known as retirement need. In theexample embodiment, retirement need is calculated as a percentage of theprojected salary at the time of retirement. In some embodiments,retirement need growth is projected based on inflation. For example,after the initial retirement need is calculated, the amount may grow bya projected inflation rate for each year of retirement. In otherembodiments, retirement need growth is projected based on anage-dependent growth factor determined by replacement income module 212.For example, expenses may grow more rapidly based on age due tohealthcare costs.

In certain embodiments, replacement income module 212 may adjustretirement need based on the life expectancy of the user, and a spouseof the user. The retirement need may decrease after the life expectancyof one household member. For example, the retirement need in years afterthe life expectancy of a household member may be decreased by aretirement need discount factor. More specifically, replacement incomemodule 212 may retrieve age and life expectancy data from GUI computersystem 114, and determine the number of years with a reduced household.

Users may have multiple accounts (e.g., Taxable Accounts, Post-TaxAccounts, Pre-Tax Accounts), and withdrawals from these accounts mayhave specific tax implications. Distributions module 214 is configuredto determine when there is a net income need, and make distributionsfrom specific accounts based on tax and/or penalty factors.Distributions module 214 calculates net income need by subtractingretirement need from the combination of investment income and benefits(e.g., social security).

Distributions module 214 is configured to determine an account ordering.For each account, distributions module 214 is configured to determine ifa withdrawal penalty applies (e.g., an early withdrawal penalty) and/ora tax penalty. In some embodiments, distributions module 214 mayevaluate specialized accounts, such as health savings accounts. Accountswithout an early withdrawal and/or tax penalty may be ordered beforeother accounts. For example, an account comprised of post-taxcontributions may be ordered before an account where taxes arecalculated on distributions. For accounts of comparable tax/penaltystatus, older accounts may be ranked before younger accounts.

Distributions are calculated in response to net income need fromaccounts, starting from the account with the lowest tax/penalty ranking,until the net income need is met. For example, given a net income needof $500 after considering social security, the $500 may be withdrawnfrom a post-tax account that does not have an early withdrawal penalty.

In some embodiments, user profile data may include information about theuser such as, for example, birth date, gender, salary, state ofresidence, current employee savings rate, plan match, profit sharing,retirement age, pension information, social security information (e.g.,estimated social security amount, start age), balance information andcurrent fund holdings, and loan information.

FIG. 3 illustrates an exemplary interface outline 300 for a graphicaluser interface (GUI) 301 implemented by GUI computer system 114 for thefinancial planning system driven by the at least one planning engine150. GUI 301, such as a web interface, is configured to interface withplanning engine 150 to receive and present financial data to a user. Insome embodiments, each planning engine 150 provides an API, throughwhich GUI 301 may send profile data retrieved from database 120 for auser and receive financial data and projections from the respectiveplanning engine 150. In the exemplary embodiment, GUI computer system114 is configured to generate GUI 301, as a series of a webpages,wherein the webpages contain instructions to capture financial data,store the financial data in database 120, and transmit financial data asneeded to planning engine 150. A brief description of each page will beprovided with respect to FIG. 3, and additional detail about certainpages will be described with respect to later figures.

In the exemplary embodiment, for at least some of the data entry/editfields of GUI 301 discussed herein, GUI computer system 114 isconfigured to validate the information entered by a user. For example,the data entry/edit fields are configured to check user entries againstminimum/maximum amounts or unaccepted characters. If information enteredin the fields fails validation, GUI 301 is configured to display a redvisual text to notify the user that the information entered has failedvalidation, and thus the information must be corrected in order toenable GUI computer system 114 to store the information.

In the exemplary embodiment, GUI computer system 114 receives a requestfrom a user computer device, such as user computing device 112. GUIcomputer system 114 is configured to cause to be displayed disclosurepage 302 to the user computing device 112. Disclosure page 302 displaysdisclaimer information and allows the user to continue to anintroductory page 304.

Introductory page 304 is configured as an introductory page thatdisplays basic data about the user's retirement accounts. Introductorypage 304 allows the user to select an option to learn more about thelevels of service available from the financial planning systemassociated with GUI computer system 114. Introductory page 304 alsoallows the user to select an option to enroll for enhanced services inthe financial planning program. In one embodiment, the user selects theoption to learn more about the financial planning system, and GUI 301causes to be displayed an “about” page 308. In another embodiment, theuser selects the option to enroll in the enhanced services, and GUIcomputer system 114 causes to be displayed a registration page 310.

About page 308 displays information about the financial planning systemand also allows the user to access registration page 310.

Registration page 310 allows the user to register for the enhancedservices. Registration page 310 captures demographic and salary datafrom the user and displays a summary of fees for utilizing the enhancedservices. Registration page 310 also allows the user to agree to enrollin the enhanced services, in which case GUI 301 causes a registrationconfirmation page 312 to be displayed on the user computing device 112.

Registration confirmation page 312 displays a notice to the userconfirming the success of registering for the enhanced services, as wellas a current list of allocations associated with the user. Registrationconfirmation page 312 also allows the user to access the retirementdashboard, in which case planning engine 150 causes to be displayeddashboard page 314. Further, after the user agrees to enroll in theenhanced services through registration page 110, a request to return tothe home page will cause to be displayed home page 334. Home page 334displays financial goals and projections associated with the user, basedon user profile data and account data received from the user.

Home page 334 is configured to display a homepage associated with theuser. The homepage displays financial goals and projections associatedwith the user, based on user profile data and account data received fromthe user. Home page 334 maintains an appearance and feel similar tointroductory page 304. For example, Home page 334 and introductory page304 each include financial projections generated by the projection andoptimization modules 152 of the at least one planning engine 150 basedon a first set of data fields in the user profile data. For example,Home page 334 and introductory page 304 each display a graphic whichrepresents that percentage of a savings goal that a user has achieved.Further, Home page 334 and introductory page 304 each allow the user toselect the aforementioned graphic, which causes to be displayed a goalsquick view page 336. Goals quick view page 336 displays more detailedinformation about a user's retirement goals, and allows the user toupdate certain pieces of information. This functionality is available toboth users who receive the first, basic level of functionality of GUI301 and the at least one planning engine 150, and users who haveenrolled in the second, enhanced level of functionality of GUI 301 andthe at least one planning engine 150.

Home page 334 has some differences from introductory page 304, relatingto enhanced services. For example, Home page 334 allows the user toselect a link to the “dashboard”, which causes to be displayed Dashboardpage 314. As used herein, the term “link” may be used to refer to ahyperlink, a button, or other such virtual component that allows a userto interact with GUI 301 to access (e.g., “link to”) additional ordifferent content. Moreover, in some embodiments, Home page 334 allowsthe user to add information to database 120 regarding members of theuser's household, which functionality is not available from introductorypage 304.

Dashboard page 314 allows the user to navigate among a plurality ofmodules associated with the enhanced services that allow a user tomanage different aspects of the user's financial planning. Dashboardpage 314 allows the user to select at least one of an about me page 316,an investments page 326, an income planning page 328, a savings page330, an opportunities page 332, an un-enroll page 334, an activitysummary page 336, and a my goal page 338. In response to receiving aselection of a given page, GUI 301 causes to be displayed thecorresponding page on the user computing device 112. These pages enablethe user to input or edit different aspects of user profile data,corresponding to values in respective database fields of the userprofile in database 120, subject to constraints and validations appliedby GUI computer system 114.

About me page 316 allows the user to access a my family page 318, anassets page 320, an income in retirement page 322, and a savings goalspage 324. A user selection of a given page causes GUI 301 to cause to bedisplayed the corresponding page to the user computing device 112.

My family page 318 generally captures personal user profile data (e.g.demographic data, spouse and dependents data, and salary data) from theuser. In some embodiments, my family page 318 directs the user through anumber of data input pages which are configured to request and captureuser profile data from the user. When a user completes the data entryrequests, my family page 318 automatically directs the user to assetspage 320. Assets page 320 captures asset data (e.g. asset identifiersand asset compositions) for outside accounts and other long-term assetsfrom the user and allows the user to access income in retirement page322.

Income in retirement page 322 allows the user to input data aboutsources of income the user expects to receive in retirement. Income inretirement page 322 captures data (e.g. income data and benefit data)from the user and allows the user to select which member of the familyis associated with the captured data. When a user completes the dataentry requests, income in retirement page 322 directs the user tosavings goals page 324.

Savings goals page 324 allows the user to input data about the user'ssavings goals. For example, the user may input data regarding a child'swedding that the user expects to have to pay for during retirement.Savings goals page 324 captures user profile data (e.g. financial needsto be met in retirement, apart from the steady state) from the user andallows the user to select which member of the family is associated withthe captured data. When a user completes the data entry requests,savings goals page 324 directs the user back to about me page 316.

Investments page 326 displays an overview of financial projectionsassociated with a user's portfolio, wherein the financial projectionsare based on user profile data. Investments page 326 also allows theuser to select between a plurality of data displays. For example,investments page 326 allows the user to select at least one of anequities/bonds display, an asset class display, and a funds display.Investments page 326 also captures user account preferences (e.g. riskpreference data).

Income planning page 328 displays information related to a user's drawfrom the financial account, and from outside accounts and otherbenefits, during retirement. For example, income planning page 328displays a graphical projection of whether the user will achievefinancial goals based on user profile data and account data. Incomeplanning page 328 is configured to display an alert if an output fromplanning engine 150 indicates that the user is projected to fall shortof financial goals. Income planning page 328 also allows the user tomodel alternative plans by entering alternative user profile data, suchas modified financial goals and retirement dates.

Savings page 330 allows the user to view different contribution rateamounts and types, and select between the contribution rate amounts andtypes. Savings page 330 displays a recommended contribution rate basedon user profile data and account data and captures contribution databased on a user selection of a given contribution rate.

Opportunities page 332 allows the user to respond to recommendationsgenerated by system 100. Un-enroll page 334 allows a registered user toun-register from the enhanced services, for example to revert to basicservices. Activity summary page 336 allows the user to review recenttransactions.

My goal page 338 allows the user to set retirement goals. My goal page338 captures user profile data such as financial goal data and desiredretirement age. My goal page 338 also displays a household income goalbased on the financial goal data for different members of a household.

FIG. 4 depicts an example introductory page 400, such as introductorypage 204 of GUI 301, which is generated and transmitted by planningengine 150. In the illustrated embodiment, introductory page 400 isshown as displayed for a base-level user. Introductory page 400 providesa top-level menu 401 that appears in a substantially identical formatand a substantially identical location for both base-level andenhanced-level users. Introductory page 400 is configured to displaybasic information associated with the user's account, such as the user'sfinancial goals, progress toward the financial goals, a total accountbalance, or high-level user preferences. In some embodiments, the userinformation on introductory page 400 is obtained from the employer, asone of financial data sources 116, based on information provided by theemployee when the user was hired as an employee and/or when the userbecomes eligible for participation in the 401(k) plan associated withthe financial account. For example, the data may be obtained from arecordkeeper of the 401(k) plan. Introductory page 400 also allows theuser to change certain user preferences and/or update data in a firstset of data fields of the user's profile in database 120, obtain moreinformation about the levels of service available for the financialaccount, and register for an enhanced service level provided by thefinancial planning system. GUI computer system 114 is configured toreceive a log-in request from the user and, based on the log-in request,cause to be displayed introductory page 400 to a user computing device112.

Introductory page 400 is configured to transmit values from the userprofile for the first set of data fields to planning engine 150, and todisplay financial projections generated by planning engine 150 using theuser's values from the first set of data fields. In some embodiments,introductory page 400 is configured to call a single planning engine 150for basic financial projections, regardless of whether the user isregistered for basic services or enhanced services. This facilitatesprotecting a user who is newly registered for enhanced services fromseeing significant numerical changes or formatting changes upon loggingin, thereby increasing an initial user satisfaction with the enhancedservices and increasing an adoption and retention rate for the enhancedservices. For example, in some embodiments, the planning engine 150includes multiple planning engines each supporting a different level ofservices for the financial account, and introductory page 400 isconfigured to call a first planning engine 150 for basic financialprojections, regardless of whether the user is registered for basicservices or enhanced services. Alternatively, the at least one planningengine 150 is a single planning engine 150.

Introductory page 400 is configured to display total account balance 404and benefits plan 406 for the user's financial account. Introductorypage 400 is also configured to display goal summary 402 and estimatedincome 416 to both base-level and enhanced-level users based onfinancial projections generated by planning engine 150. Specifically,planning engine 150 generates estimated retirement income 416 based onuser profile data and account data, and generates goal summary (or“comparison”) 402 based on a comparison of estimated income 416 to auser goal for retirement, as derived from database 120 from user profiledata (e.g. an estimated monthly income goal, an estimated retirementgoal). The goal summary 402 is configured to appear in substantiallyidentical format and substantially identical location on introductorypage 400 for both base-level and enhanced-level users, as shown in FIG.5. Goal summary 402 is also configured to capture user input requestingaccess to edit fields in the user profile stored in database 120.Specifically, goal summary 402 is configured to transmit a user requestto GUI 301, which causes to be displayed a goals configuration displaysuch as goals configuration display 600 (shown in FIG. 6) and goalsconfiguration display 700 (shown in FIG. 7).

Planning engine 150 is further configured to generate income components408, 410, and 412 based on user profile data and account data. In theexemplary embodiment, income component 408 represents income generatedfrom a savings account, a component of investment income which iscalculated by investment income module 206 (shown in FIG. 2). Incomecomponents 410 and 412 represent employer contributions and socialsecurity benefits respectively, both of which are components of abenefits plan value, which is calculated by benefits module 210 (shownin FIG. 2). In an alternative embodiment, income component 410, whichrepresents employer contributions, is a component of investment incomewhich is calculated by investment income module 206. Planning engine 150is further configured to determine income gap 414 based on a comparisonof estimated income 416 to user-input financial goals (e.g. an estimatemonthly income goal). Using projections returned from planning engine150, GUI 301 is configured to display income tracking bar 418, which isa visual representation of income components 408, 410, and 412 andincome gap 414 using different colors on a single bar. Introductory page400 is also configured to capture a user's preferred confidence level428 for the projections. In the exemplary embodiment, the user selectsfrom two pre-determined values, and the selected value is transmitted toplanning engine 150. Planning engine 150 uses confidence level 428 as aninput for generating financial projections such as estimated income 416and income components 408, 410, and 412.

Introductory page 400 is further configured to capture user profile dataand account data through interactive sliders 424 and 426, and store thecaptured data to database 120. In an alternative embodiment,introductory page 400 is configured to capture data using any suitablegraphical control and/or to display any number of interactive sliders.In the exemplary embodiment, interactive sliders 424 and 426 allow theuser to input contribution data and retirement age data respectively. Inalternative embodiments, interactive sliders 424 and 426 capture othertypes of user profile data and/or account data. In some embodiments,interactive sliders 424 and 426 are configured to “snap” to certainintermediated pre-determined values which are generated by GUI 301. Insome embodiments, introductory page 400 displays recommended valuesand/or starting points for interactive sliders 424 and 426.

Introductory page 400 is further configured to display current slidervalues 420 and 422, which are configured to display numeric valuesrelated to the data captured by interactive sliders 424 and 426respectively. In some embodiments, slider values 420 and 422 display thenumeric value selected by interactive sliders 424 and 426 respectively.In other embodiments, slider values 420 and 422 display a valuegenerated by planning engine 150 based on at least the input capturedfrom interactive sliders 424 and 426. Introductory page 400 is furtherconfigured to display company match tracker 432, which is generated byGUI 301 based on account data such as benefits data and contributiondata.

Introductory page 400 is configured to receive user input requestingmore information about the financial planning system through a “learnmore” link 436. Learn more link 436 causes to be displayed aninformational page such as informational page 800 (shown in FIG. 8A) orabout page 208 (shown in FIG. 2).

If the user is a base-level user, introductory page 400 is configured toreceive user input requesting enrollment in enhanced services bydisplaying an enrollment request 430 to the base-level user. Enrollmentrequest 430 may be similar to “Do It For Me” link 860 (shown in FIG.8C). Enrollment request 430, when activated by the base-level user, alsocauses to be displayed an enrollment page such as registration page 900(shown in FIG. 9) or registration page 210 (shown in FIG. 2). If theuser is already an enhanced-level user, the introductory page isconfigured to provide a “Go to My Total Retirement” link (or “dashboardrequest”) 532 (as shown and described with respect to FIG. 5 below).Dashboard request 532 appears in a dashboard-link location substantiallyidentical to the location of enrollment link 430 for base-level users.

FIG. 5 depicts an example homepage 500, such as Home page 334, which iscauses to be displayed as the introductory page by GUI 301 for a userenrolled in the enhanced level service (e.g., after becoming anenhanced-level user). In other words, Homepage 500 is introductory page400 as it appears to a user 102 who is enrolled for enhanced services.Homepage 500 is configured to provide a substantially similar look andexperience to the user as introductory page 400. For example, Homepage500 includes top-level menu 501 identical to top-level menu 401. Inother words, the overall layout of homepage 500 is recognizable and/orfamiliar to user 102, based on introductory page 400 as it appeared tothe user prior to enrollment for enhanced services.

Just as in introductory page 400 in FIG. 4, Homepage 500 is configuredto display a total account balance 504 and a benefits plan 506 for theuser's financial account, as well as goal summary 502 including theidentical comparison of estimated income 516 to the user goal forretirement as in goal summary 402. Goal summary 502 is likewiseconfigured to capture user input, such as a user clicking or otherwiseselecting goal summary 502, to provide access to configure inputs usedby planning engine 150 in generating financial projections by causing tobe displayed a goals configuration display such as goals configurationdisplay 600 (shown in FIG. 6) and goals configuration display 700 (shownin FIG. 7).

GUI 301 is again configured to generate income components 508, 510, and512 based on user profile data and account data, identical to incomecomponents 408, 410, 412, and an other-assets component 518 based onother assets entered into database 120 by the user (not shown in FIG.4). Planning engine 150 is again configured to determine income gap 514based on a comparison of estimated income 516 to user-input financialgoals (e.g. an estimated monthly income goal), and GUI 301 is againconfigured to cause to be displayed an income tracking bar 520, which isa visual representation of income components 508, 510, 512, and 518 andincome gap 514 using different colors on a single bar. Homepage 500 isalso configured to capture a user's preferred confidence level 530 forfinancial prediction. In the exemplary embodiment, the user selects fromtwo pre-determined values, and the selected value is transmitted toplanning engine 150. Planning engine 150 uses confidence level 530 as aninput for generating financial projections, such as estimated income 516and income components 508, 510, 512, and 518.

Homepage 500 is likewise configured to capture user profile data andaccount data through interactive sliders 526 and 528, and to displaycurrent slider values 522 and 524 and company match tracker 534,identical to those displays as shown in FIG. 4.

As noted above, in contrast to introductory page 400 as it appears tobase-level users, Homepage 500 is configured to receive user input forenhanced-level users requesting access to a dashboard through dashboardrequest 532. Dashboard request 532 causes to be displayed a dashboard,such as dashboard 1100 (shown in FIG. 11) or dashboard page 214 (shownin FIG. 2), which provides access for enhanced-level users to theenhanced-level services as described below. In the example embodiment,dashboard request 532 is displayed on homepage 500 in a substantiallyidentical location as enrollment request 430 appears on introductorypage 400. Thus, the option to register for base-level users throughenrollment request 430 is effectively replaced by the dashboard request532 on a similar page once the user becomes an enhanced-level user. Forexample, newly registered users have a familiar starting point fromwhich to move forward to the changes and benefits of registration in anotherwise familiar environment within GUI 301.

FIG. 6 depicts goals configuration display 600 of GUI 301, which allowsa user to change (e.g., edit) values for certain data fields in database120, which are to be used as inputs used by planning engine 150 togenerate financial projections. Display 600 is caused to be displayedbased on a user request received through a goal summary icon, such asgoal summary 402 (shown in FIG. 4) and goal summary 502 (shown in FIG.5). In the example embodiment, display 600 is configured as a pop-upoverlay displaying over homepage 500 or introductory page 400 to displayinputs used by planning engine 150 in calculating financial projections,such as income goal 608 and goal summaries 402, 502, and 602. Display600 is further configured to capture user inputs, such as user profiledata and account data (e.g., current income, additional compensation,date of birth, portion of current income desired in retirement), andstore the data in database 120.

Display 600 is configured to display a goal summary 602, which issubstantially similar to goal summaries 402 and 502. In someembodiments, goal summary 602 is configured to update goal summary 602based on captured user input. Display 600 is further configured todisplay tabs for family members 604 and 606. GUI 301 causes to bedisplayed family member tabs 604 and 606 that enable editing ofcorresponding user profile data in database 120, which also can beinitiated from dashboard 1100 (shown in FIG. 11) for an enhanced-leveluser. Display 600 is configured to allow the user to switch between adisplay for each family member associated with tabs 604 or 606.Specifically, display 600 is configured to toggle between informationspecific to each family member in the displayed data fields based onreceiving user input selecting the corresponding family member tab 604or 606. In some embodiments, GUI 301 enables the user to toggle betweenmore or fewer than two plurality of family member tabs, wherein thenumber of family members is based on user profile data.

Display 600 is configured to display income goal 608, which is generatedby GUI computer system 114 based on financial goals captured from theuser, who is associated with the first tab 604. Display 600 is furtherconfigured to capture current income data 610, additional compensationdata 612, date of birth 614, retirement income amount data 616, incomeformat data 618, and income period data 620 with respect to familymember tab 604 (i.e., the user). For example, retirement income amountdata 616 is expressed in a format 618 of a percent of pre-retirementincome. In the exemplary embodiment, the current income 610 andadditional compensation 612 are summed and multiplied by the retirementincome amount data 616. Income goal 608 is calculated based on incomeperiod data 620 applied to the sum of current income 610 andcompensation 612, as modified by retirement income amount 616.

In some embodiments, income format data 618 captured through display 600causes display 600 to alter the input options for income amount data616. For example, a user may select “$” for input retirement format data618, in which case display 600 may allow the user to input income amountdata 616 as a dollar amount. In another example, a user may select “%”for income format data 618, in which case display 600 may allow the userto input income retirement amount data 616 as a percentage of currentincome 610.

Display 600 is also configured to receive a user request to save anyupdated inputs through a save request 622. Save request 622 causesplanning display 600 to store any data input by a user in database 120.Save request 622 also causes to be displayed an updated underlying page,such as introductory page 400 (shown in FIG. 4) or homepage 500 (shownin FIG. 5). Alternatively, a cancel request 624 discards any changed andreverts to non-updated introductory page 400 or homepage 500.

FIG. 7 depicts goals configuration display 600 having second member tab606 selected. With second family member tab 606 selected, display 600 isstill configured to display goal summary 602 and update goal summary 602based on captured user input. Display 600 is further configured todisplay family members tab 604 and 606 to allow the user to togglebetween a display for each family member 604 or 606. Moreover, display600 is configured to display income goal 708 based on financial goalscaptured from the user with respect to the second family member. Display600 is further configured to capture current income data 710, additionalcompensation data 712, date of birth 714, retirement income amount data716, income format data 718, and income period data 720 with respect tothe second family member. In the exemplary embodiment, the currentincome 710 and additional compensation 712 are summed and modified bythe retirement income amount data 716 as described above to calculateincome goal 708.

When second family member tab 606 is selected, display 700 is also stillconfigured to receive a user request to save any updated inputs throughsave request 622 or discard changes via cancel request 624.

FIG. 8A depicts an exemplary informational page 800 of GUI 301 whichprovides a user with a tabular comparison of services available throughthe financial planning system. Informational page 800 identifies variousservices available to enhanced-level users (e.g., under the “ManagedAccounts” column) and options for online advice available through anonline advice service. Informational page 800 is caused to be displayedupon reception of user input requesting more information, such as learnmore link 436 (depicted in FIG. 4). In the exemplary embodiment,informational page 800 is configured to display a comparison table 802,which identifies services available through the financial planningsystem, basic services available to unregistered users, and servicesavailable through both. Informational page 800 is also configured toallow the user to learn more about the enhanced services via a continuelink 810, or to register for online advice via an online advice link812.

FIG. 8B depicts an exemplary informational sub-page 820 of GUI 301 whichprovides a user with more information about the financial planningsystem. Informational sub-page 800 is caused to be displayed uponreception of user input requesting more information, such as continuelink 810.

In the exemplary embodiment, informational sub-page 820 is configured todisplay a system overview 822, which describes some aspects of thefinancial planning system relevant to a potential consumer or user.Informational sub-page 820 is also configured to display a videooverview link 824, which is configured to display a video furtherdescribing the financial planning system. Informational sub-page 820 isalso configured allow the user to proceed to a registration page, suchas registration page 210 (shown in FIG. 2) or registration page 900(shown in FIG. 9) based on receiving user input through a registrationlink 830. In the example embodiment, registration link 830 appears inmultiple locations on informational sub-page 820 to facilitate ease ofregistration for the enhanced services. Alternatively, informationalsub-page 820 includes any suitable number of registration links 830.

In alternative embodiments, informational sub-page 820 is generated andtransmitted by planning engine 150 as part of informational page 800,directly upon reception of user input requesting more information, suchas learn more link 436 (depicted in FIG. 4), or in response to any othersuitable link or request.

FIG. 8C depicts another exemplary informational page 850 of GUI 301which provides a user with a comparison of services available throughthe financial planning system. Informational page 850 is caused to bedisplayed by user selection of the “guidance” link in top-level menu401/501 (shown in FIGS. 4 and 5). Informational page 850 providesguidance links that allow for base-level users to directly administertheir own financial account through a “Do It Myself” link 852, allowingthe user to select funds for their own plan. Informational page 850 alsoallows users to access online advice through a “Help Me Do It” link 854or to choose target dated funds through link 856.

In the example embodiment, the informational page 850 also allows thebase-level user to enroll in (e.g., register for) the enhanced level ofservices by providing an instance of enrollment link 830 in a “Do It ForMe” section 860. The enhanced service level allows enhanced-level usersaccess to additional plan management functionality provided by orthrough the at least one planning engine 150. FIGS. 9 and 10 describeaspects of user enrollment in the enhanced service level. Aspects of theenhanced service level functionality are described below with respect toFIG. 11 and the succeeding figures.

FIG. 9 depicts registration page 900 of GUI 301. Registration page 900allows a user to register for the enhanced service level and inputrelevant personal and financial information. Registration page 900 iscaused to be displayed upon reception of a user request to enroll in thefinancial planning system, such as through enrollment request 430 (shownin FIG. 4) or registration link 830 (shown in FIGS. 8B and 8C).

Registration page 900 is configured to confirm or update existing data,such as data stored in a first set of data fields in database 120associated with the basic level of service for the user, throughregistration input fields 902. In the exemplary embodiment, registrationpage 900 confirms demographic data such as first name 904, last name906, birthdate 908, state of residence 910, and gender 912. Registrationpage 900 is further configured to confirm contact data such as phonenumber 916 and email address 918. Registration page 900 is alsoconfigured to confirm income data 914. Registration page 900 isconfigured to store any updated data in database 120.

Registration page 900 is further configured to display fee table 920.Fee table 920 is generated and transmitted by planning engine 150. Inthe exemplary embodiment, fee table 920 displays values for amounts ofassets under management and associated annual rates for managing theamounts of assets. GUI 301 is configured to retrieve fee structure data,such as amounts of assets under management and associated annual rates,from a database such as database 120 (shown in FIG. 1).

Registration page 900 is also configured to receive an enrollmentagreement request for the enhanced services through enrollmentconfirmation link 922. Enrollment confirmation link 922 receives a userrequest and causes to be displayed a registration confirmation page suchas registration confirmation page 212 (shown in FIG. 2) or enrollmentconfirmation page 1000 (shown in FIG. 10). Alternatively, a user mayselect a cancel request 924 and decline to register for the enhancedservices.

FIG. 10 depicts enrollment confirmation page 1000 of GUI 301. Enrollmentconfirmation page 1000 displays confirmation of enrollment 1002 to auser. Enrollment confirmation page 1000 is also configured to displayinitial asset allocations 1004.

GUI 301 is configured to call the at least one planning engine 150 togenerate and transmit initial asset allocations 1004 upon receiving anenrollment agreement request, such as through enrollment confirmationlink 922 (shown in FIG. 9). Initial asset allocations 1004 include assetdata such as asset identifiers and asset compositions. In someembodiments, initial asset allocations 1004 are determined by returncalculations module 204 (shown in FIG. 1B) based on user profile dataand account data.

Enrollment confirmation page 1000 is configured to display additionalinformation 1006, which includes more information about the enhancedservices, steps for moving forward with the enhanced services, and/orany other information that may be useful to a newly registered user.

Enrollment confirmation page 1000 is also configured to allow the userto proceed to a dashboard page, such as Dashboard page 214 (shown inFIG. 2) or retirement dashboard 1100 (shown in FIG. 11), by receivinguser input through dashboard request 1008.

FIG. 11 depicts an exemplary dashboard 1100 of GUI 301, such asdashboard 214, provided for enhanced-level users. Dashboard 1100provides links to financial information for detailed retirementplanning. In the example embodiment, retirement goal link 1102 and aboutme link 1108 allow user 102 to edit financial goal data and user profiledata stored in database 120. Savings link 1106 and investments link 1104allow user 102 to review the status of retirement account contributionsand currently selected investments and edit related database fields.Activity summary link 1110 provides summaries of recent accountactivity. Income planning link 1112 enables the user to review and modelexpected income during retirement, and opportunities link 1114 providesuser 102 with prioritized recommendations to incrementally improve theuser's ability to meet retirement goals. For example, opportunities link1114 allows user 102 to provide targeted additional information or maketargeted changes to further optimize the account.

Savings link 1106 is, in the example embodiment, adjacent to savingsindicator 1116, which visualizes a retirement goal. For example, whereinvestment income module 164 determines that a retirement goal (or anyother financial goal) will not be met, savings indicator 1116 maydisplay as red. Activity indicator 1120 is adjacent to activity summarylink 1110, and displays a total number of instances of recent useractivity. Opportunities indicator 1122 is adjacent to opportunities link1114, and displays a total number of opportunity recommendationsavailable to user 102. About me indicator 1118 is adjacent to about melink 1108, and may display a number of alerts. For example, a totalnumber of profile alerts may be displayed in the indicator.Additionally, a number of priority alerts 1128 may also be displayed ina contrast color, such as red. Opportunity area 1126 displays a messagerecommending an identified candidate modification to the user profiledata in database 120, and an associated jump link to a page of GUI 301enabling user 102 to execute the identified candidate modification.

Dashboard page 1100 also includes an estimated income widget 1130 thatdisplays a comparison of another estimated retirement income amountgenerated by the at least one planning engine 150 to a user goal forretirement, as derived from database 120 from user profile data (e.g. anestimated monthly income goal). The estimated income amount included inestimated income widget 1130 differs from the estimated income includedin goal summary 402 (shown in FIG. 4 and also identical to goalsummaries 502, 602, 702), based on the improved projections associatedwith the enhanced services. For example, goal summary 402 relies on arelatively less complex projected before-tax income using only valuesfrom a first set of data fields in database 120. In contrast, estimatedincome widget 1130 displays a relatively more complex projectedafter-tax income based on values for both the first set of data fieldsand a second set of data fields, wherein the values for the second setof data fields from database 120 are passed to the at least one planningengine 150 solely for users enrolled in the enhanced services. In someembodiments, the at least one planning engine 150 includes a firstplanning engine that supports basic-level services and operates onvalues drawn solely from the first set of data fields, and a secondplanning engine 150 that supports enhanced-level services and operateson values drawn from both the first and second sets of data fields.Estimated income widget 1130 is programmed to update dynamically inresponse to the user 102 interacting with GUI 301 to make a change tothe user profile that impacts the projected income and/or the user goal.Accordingly, for users 102 enrolled in enhanced services, estimatedincome widget 1130 facilitates an immediate visualization by the user ofthe impact of each change implemented by the user with respect to thefinancial account.

In the example embodiment, estimated income widget 1130 also displays aprogress indicator 1132 that indicates progress to the user goal. Forexample, in FIG. 11, the user's projected retirement income isapproximately two-thirds of the user goal, and progress indicator 1132is a bar that correspondingly extends approximately two-thirds of thedisplayed width of estimated income widget 1130. Alternatively, if theuser's projected retirement income meets or exceeds the user goal,progress indicator 1132 is a bar that fills the entire displayed widthof estimated income widget 1130. Further in the example embodiment,progress indicator 1132 is a first color (e.g., green) if the user'sprojected retirement income meets or exceeds the user goal, and is asecond color (e.g., red) if the user's projected retirement income isless than the user goal. In alternative embodiments, progress indicator1132 is displayed in any suitable fashion.

Dashboard 1100 is also configured to display, in an opportunity area1126, one or more opportunities for a participant in response to GUIcomputer system 114 determining that at least one opportunity exists forimproving a performance of the participant's account. For example, GUIcomputer system 114 identifies opportunities for display in opportunityarea 1126 using an opportunity rules engine to analyze the user profilein database 120. In the example embodiment, opportunity area 1126displays a message associated with a first identified opportunity, andan opportunity indicator 1122 displayed on dashboard 1100 displays atotal number of opportunities identified by GUI computer system 114.

FIG. 12 depicts an exemplary about me page (or “user profile page”) 1200of GUI 301, such as about me page 216, which may be opened using aboutme link 1108. About me page 1200 displays an overview of data fieldsincluding personal profile information 1202, financial information 1204,and retirement expenditures information 1206. User 102 may review aboutme page 1200 to update information, or determine what information stillneeds to be provided for null fields (i.e., those fields for which theuser has yet to specify a value), to enable all projection andoptimization modules 152 to execute fully and accurately, and to updatespecific sections of information as available. For example, user 102 mayupdate salary data or add a dependent.

About me update link 1208 facilitates user 102 submitting salary data,demographic data (e.g., age, birthdate), and spouse information. Familyinformation link 1210 facilitates user 102 submitting dependent data, asshown in FIGS. 13-16, such as the names and birthdates of dependents.Profile information 1202 may summarize previously submitted user profiledata, such as a name and salary.

Financial information 1204 includes social security link 1212, assetslink 1214, and income in retirement link 1216. Financial information1204 may include preview data, such as estimated social securitybenefits and indicators of benefit plans. Social security link 1212causes to be displayed social security page 4600 (shown in FIG. 46),which enables the user to edit a benefit start age and an expectedbenefit. Social security page 4600 includes a “Use our estimated monthlybenefit” option, which displays a social security benefit table 4700(shown in FIG. 47) if selected. Retirement expenditures information 1206includes savings goals link 1218, such that user 102 may define asavings goal to meet a discrete, one-time expense expected to ariseduring retirement, such as a child's wedding or a particular vacationplan.

FIG. 13 depicts an exemplary spouse status page 1300 of GUI 301, whichmay be opened via about me link 1208, and facilitates user 102 selectingif they have a spouse or partner. More specifically, user 102 mayidentify a spouse or partner using selector 1302. FIG. 14 depicts theexemplary spouse status page 1300 with a spouse detail region 1400. Inresponse to indicating a spouse/partner, spouse status page 1300 isenlarged to include spouse detail region 1400 to capture spouse data, asshown in FIG. 14.

Spouse detail region 1400 is configured to capture spouse data from user102. In the example embodiment, in response to user 102 indicating thathe or/she has a partner using selector 1302, and spouse detail region1400 prompts user 102 for additional spouse data, such as first name1404, birthdate 1406, gender 1408, salary 1412, desired retirement age(e.g., retirement goal) 1414, and income replacement 1416. Spouse datacaptured by spouse detail region 1400 may be used by replacement incomemodule 212 and benefits module 210 to calculate income needed inretirement and/or spouse-based social security benefits.

Spousal status page 1300 is configured to facilitate the transmission ofspouse data through continuation request 1420. Continuation request 1420is also configured to facilitate access to another page, such asdependent status page 1500 (shown in FIG. 15). Alternatively, the backbutton 1422 may be used to discard changes.

FIG. 15 depicts an exemplary dependent status page 1500. Dependentstatus page 1500 of GUI 301 may be opened using about my familyinformation link 1210 and facilitates user 102 identifying if they havedependents, such as young children or special needs relatives. Morespecifically, user 102 may identify dependents using selector 1502. FIG.16 depicts the dependent status page 1500 with a dependent detail region1600. In response to indicating at least one dependent using selector1502, dependent status page enlarges to include dependent detail region1600 to capture dependent data, as shown in FIG. 16.

Dependent detail region 1600 is configured to capture dependent datafrom user 102, such as the name and age of any dependents. In theexample embodiment, two dependents are reported, with ages 12 and 7.Dependent detail region 1600 includes first name fields 1604, andadjacent birthdate fields 1606, for a number of potential dependents.Fields for additional dependents may be added with link 1612. Dependentdata is transmitted to server computing device 114 in response to savelink 1614 being selected. Alternatively, changes may be discarded usingback link 1616.

FIG. 17 depicts an exemplary asset status page 1700. Asset status page1700 of GUI 301 may be opened using assets link 1214 and facilitatesuser 102 reporting assets, such as other retirement plans, pensions, andthe like. For example, user 102 may report an individual retirementaccount, which may be used to project additional investment income inretirement. Asset status page 1700 displays asset examples 1702 to user102. Add now link 1704 facilitates user 102 reporting detailedinvestment assets, which may be used by investment income module 206.

After selecting add now link 1704, user 102 is directed to an add assetpage 5000, a first embodiment of which is shown in FIG. 50 and analternative “pop-up” embodiment 5600 of which is shown in FIG. 56, whereuser 102 has the ability to enter data corresponding to the asset beingadded. For example, user 102 may enter information corresponding to thefollowing data fields: the account owner, the account type, the accountprovider, what type of contribution (e.g., pre-tax contribution, Rothcontribution, post-tax contribution, mix contribution, and nocontributions) participant is currently contributing, the amount of thecontribution if there is one, how is the account invested, and theaccount balance. GUI computer system 114 uses the account provider fieldto differentiate between multiple accounts that the participant may holdand are stored in database 120. When entering the account provider, GUI301 is configured to perform an auto complete list on the accountprovider field, so that user 102 may select from the account providerfrom a dropdown list. If the account provider is not listed on the autocomplete list, user 102 may enter the account provider manually. Otherdata fields may be configured to display an auto complete list thatmitigates incorrect data entry enabling the system to collect and storeaccurate data. Details of other data entry fields on the add asset page5000 are shown in FIGS. 51-53. In some embodiments, GUI 301 furtherenables a user to identify and link existing investment accounts held bythe user at third-party institutions, as shown in FIGS. 48 and 49. Another-assets summary page 5400 after data entry is completed isillustrated in FIG. 54.

FIG. 18 depicts an exemplary supplemental income page 1800. Supplementalincome page 1800 of GUI 301 may be opened using income in retirementlink 1216 and facilitates user 102 identifying supplemental retirementincome, such as part time employment or rental income. For example,seasonal rental income may be reported, which may offset the need forinvestment retirement income. Supplemental income page 1800 includesincome examples 1802. Yes link 1804 facilitates user 102 reportingretirement income, which may be used by replacement supplemental incomemodule 212.

FIG. 19 depicts an exemplary supplemental income detail page 1900.Supplemental income detail page 1900 of GUI 301 may be opened using yeslink 1804, and facilitates user 102 detailing supplemental retirementincome. For example, projected hobby income during retirement may bereported, which may offset expenses in retirement. In some embodiments,replacement income module 212 adjusts supplemental income based oninflation. User 102 may identify user 102 or the user's spouse as theincome source using earner identifier 1902, and provide incomedescription 1904. User 102 further identifies if the income is a pension1908, and if the income is taxable 1914. Based on pension identifier1908 and taxable identifier 1914, estimated annual amount 1906 may beadjusted. More specifically, replacement income module 212 may adjustamount 1906 based on cost of living adjustment identifier 1910, andadjustment amount 1912. Estimated dates of retirement 1916 and lifeexpectancy 1918 may also be input for use by projection and optimizationmodules 152.

Supplemental income detail page 1900 is configured to facilitate thetransmission of supplemental income data through save preferences button1920. Save preferences button 1920 is also configured to facilitateaccess to another page, such as supplemental income page 1800 (shown inFIG. 18). Alternatively, the cancel button 1922 may be used to discardchanges.

FIG. 20 depicts an exemplary supplemental income summary region 2000 asa part of the supplemental income page 1800. In response to entry ofsupplemental income using page 1900, supplemental income page 1800 isupdated to include supplemental income summary region 2000, which isconfigured to display a summary of supplemental retirement incomeinformation submitted by user 102. For example, previously submittedsources of supplemental retirement income may be displayed in a list. Inthe example embodiment, the display includes a supplemental incomeidentifier 2002, supplemental income amount 2004, and date updated 2006for each source of supplemental income previously input by the user. Forexample, supplemental income identifier 2002 includes the name of user102 received from user identifier 1902 (shown in FIG. 19) and thedescription of the supplemental income received from income description1904 (shown in FIG. 19). Supplemental income amount 2004 includes theestimated annual amount of income received from estimated annual amount1906 (shown in FIG. 19.).

Supplemental income summary region 2000 is also configured to allow theuser to add more sources of supplemental income through add incomerequest 2008. In some embodiments, add income request 2008 is configuredto bring the user to supplemental income detail page 1900 (shown in FIG.19). Supplemental income summary region 2000 is further configured toallow the user to complete the income in retirement reporting processthrough completion button 2010. Completion button 2010 allows the userto access another page in the financial advisory system interface, suchas savings goals page 224 or savings goals page 2100.

FIG. 21 illustrates savings goals page 2100 of GUI 301, which may beopened using savings goals link 1218 and is configured to allow user 102to add additional savings goals which may or may not be related toretirement. For example, savings goals page 2100 allows user 102 to adda goal to save a certain amount of money for a dependent's wedding by acertain date in the future. Savings goals page 2100 is configured tocapture information from the user, including a name for the goal throughgoal description input 2102, a goal amount through goal amount input2104, and a goal date through estimated goal date inputs 2106, 2108, and2110. Savings goals page 2100 is also configured to allow the user tosave the input information through save button 2112, or alternativelydiscard any changes using cancel button 2114. Save button 2112 is alsoconfigured to allow the user to access another page in the financialadvisory system interface, such as savings goals summary 2200.

FIG. 22 illustrates savings goals summary page 2200 of GUI 301, which isconfigured to display a summary of savings goals input by user 102 inresponse to selection of save button 2112. For example, previouslysubmitted savings goals may be displayed in a list. In the exemplaryembodiment, GUI 301 causes to be displayed a savings goal identifier2202, savings goal amount 2204, savings goal date 2206, and a dateupdated 2208 for each savings goal previously input by the user. Forexample, savings goal identifier 2202 includes the name for the goalcaptured by goal description input 2102 (shown in FIG. 21). Savings goalamount 2204 includes the goal amount captured by goal amount input 2104(shown in FIG. 21). Savings goal date 2206 includes the goal datecaptured through estimated goal date inputs 2106, 2108, and 2110 (allshown in FIG. 21).

Savings goals summary page 2200 is also configured to allow the user toadd more savings goals through add a goal request 2210. In someembodiments, add a goal request 2210 is configured to bring the user tosavings goals page 2100 (shown in FIG. 21). Savings goals summary page2200 is further configured to allow the user to complete the savingsgoals reporting process through completion button 2212. Completionbutton 2212 allows the user to access another page in GUI 301, such asinvestments page 226 or investments page 2300.

In the example embodiment, each of About me page 1200, retirementsummary page 2000, and savings goals summary page 2200 includesestimated income widget 1130, as discussed above. Thus, on each of thesepages, the user is provided with an immediate, dynamically updatedsummary of the impact of each update to database fields related topersonal profile information 1202, financial information 1204, andretirement expenditures information 1206, without requiring the user tonavigate back to dashboard page 1100 or a different account summarypage.

FIG. 23 depicts investments page 2300 of GUI 301, which may be openedusing investments link 1104 (shown in FIG. 11) and displays graphicaland numeric descriptions of the composition of the user's 102 financialaccount. The investments page 2300 allows users to view aspects of theircurrent investment strategy. The user can view their investments at thetotal portfolio level as well as view the details of each of theiraccounts. The account detail view displays all of the user's accountsthat are associated with a group client, as well as any outside accountsthat they have entered. The user may also update their outside assetsfrom an account details view. GUI 301 causes to be displayed oninvestments page 2300 financial information based on user profile dataand account data. Specifically, investments page 2300 is configured todisplay asset data, such as bond and equity composition 2304 of user's102 assets, and optimized allocation strategy 2316.

In some embodiments, bond and equity composition 2304 is determined byreturn calculations module 204 (shown in FIG. 2) based on asset datasuch as asset identifiers and asset compositions. Planning engine 150,in some embodiments through return calculations module 204, isconfigured to generate a graphic composition display 2306 whichgraphically displays the adjacent numerical values.

Investments page 2300 is also configured to allow the user to selectfrom a number of ways to display financial information. Specifically,investments page 2300 includes display options 2308, 2310, and 2312. Inthe exemplary embodiment, display option 2308 is configured to displaybond and equity composition 2304 through investments page 2300, as shownin FIG. 23. FIG. 24 depicts an exemplary asset class composition 2404within the investments page 2300. Display option 2310 is configured todisplay asset class composition 2404 both numerically and graphicallyvia graphic composition display 2306. FIG. 25 depicts an exemplary fundcomposition 2504 within the investments page 2300. Display option 2312is configured to display fund composition 2504 both numerically andgraphically via graphic composition display 2306.

Investments page 2300 is also configured to display a stability graphsection illustrating a stability of the selected investment strategyover time in a “glide path” 2314, which displays a graphicalrepresentation of asset allocation (e.g., ordinate or Y-axis, in unitsof risk level) over time (e.g., abscissa or X-axis, in units of time).Optimized allocation strategy 2316 represents the optimal assetallocation over time. Glide path 2314 shows how the asset allocation oftheir enrolled accounts will be allocated to fixed income from thecurrent year until life expectancy, illustrating investment strategystability over time for the recommended investment strategy. In someembodiments, glide path 2314 may be modified with an override risk level(e.g., as shown and described below with respect to FIG. 27). Optimizedallocation strategy 2316 is determined by planning engine 150, in someembodiments by return calculations module 204, based on user profiledata and account data, such as demographic data (e.g. age) and assetdata. In the example embodiment, the ordinate includes designations ofinvestment strategy risk graded from most aggressive at the abscissa tomost conservative away from the abscissa, which configures glide path2314 to directly illustrate to the user an increase in stability overtime.

Investments page 2300 is further configured to facilitate user 102viewing alternative financial information through detail selection 2302.Detail selection 2302 allows the user to select between differentoptions for the type of information displayed on investments page 2300.Investments page 2300 is also configured to facilitate userconfiguration of settings through constraints option 2318. Constraintsoption 2318 is configured transmit to another web page, such asinvestment constraints page 2600 (shown in FIGS. 26 and 27) of GUI 301,to user 102. In some embodiments, asset class composition 2404 isdetermined by return calculations module 204 (shown in FIG. 1B) based onasset data such as asset identifiers and asset compositions.

Investment page 2300 is also configured to enable user 102 to select,for example, composition display 2306, such as by hovering a pointerover composition display 2306, to view an investment type andcorresponding percentage of the total investments depicted incomposition display 206. For example, user 102 may hover overcomposition display 2306, such as a pie chart, where the color of theregion being hovered enhances and/or changes, and a percentage and typeof investment of the region being hovered are displayed.

FIG. 26 depicts an exemplary constraints page 2600 for updatingpreferred constraints used by planning engine 150 for determiningfinancial projections. Specifically, constraints page 2600 facilitatesthe user 102 selecting an investment strategy preference and anallocation preference. In the exemplary embodiment, user 102 can selectfrom two investment strategy preferences: optimization option 2602 ormanual option 2604. Optimization option 2602 is configured to causeplanning engine 150 to determine an optimized allocation strategy basedon user profile data and account data, such as age and assetcomposition. In some embodiments, planning engine 150 determines theoptimal asset allocation strategy through return calculations module 204(shown in FIG. 1B). FIG. 27 depicts an exemplary strategy selectionoptions 2706 and strategy selection indicators 2708 within theconstraints page 2600. Selection of manual option 2604 enlargesconstraints page 2600 to display allocation options, such as strategyselection options 2706 labeled with strategy selection indicators 2708(shown in FIG. 27) to facilitate the manual selection of a particularinvestment strategy by user 102. In the exemplary embodiment, strategyselection options 2706 are risk-based investment strategies based on apercentage of user's 102 portfolio which is invested in equities vsbonds. For example, a “very aggressive” strategy indicates a preferencefor 95% equities, while a “moderate” strategy indicates a preference for59% equities. Planning engine 150, using return calculations module 204in some embodiments, determines asset allocations based on the selectedstrategy option and other user profile data and account data.

In an alternative embodiment, strategy selection options 2706 areinvestment strategies based on a percentage of a user's profile which isinvested in a particular asset class or fund. For example, a “veryaggressive” strategy may indicate a preference for 50% of the portfolioto be placed in tech stocks. In another example, a “moderate” strategymay indicate a preference for 50% of the portfolio to be spread outevenly among a variety of funds.

Constraints page 2600 is configured to facilitate the transmission ofinvestment strategy preference through save preferences button 2606.Save preferences button 2606 is also configured to facilitate access toanother webpage, such as strategy change summary 2800 (shown in FIG.28). Alternatively, the back button 2608 may be used to discard changes.

FIG. 28 depicts an exemplary strategy change summary page 2800 of GUI301 for displaying a summary of changes made to a user's 102 investmentstrategy in response to selection of save preferences button 2606. Inthe example embodiment, strategy change summary page 2800 displays asummary of changes to constraint preferences, for example, choosing adifferent optimization option 2602 or 2604 (shown in FIG. 26) or adifferent strategy selection option 2706 (shown in FIG. 27).

Strategy change summary page 2800 is configured to display a previousstrategy indicator 2802 and a current strategy indicator 2804, which areupdated based on changes to the investment strategy selected by user102. Strategy change summary page 2800 is further configured to displaychange confirmation 2806. Change confirmation 2806 includes confirmationinformation which may be helpful for facilitating documentation of thechange of strategy. In the example embodiment, change confirmation 2806includes a date and time, a confirmation number, and an affected plan.

Strategy change summary 2800 is also configured to facilitate access toanother webpage, such as update 2900 to investments page 2200, throughcontinue request 2808.

FIG. 29 depicts an exemplary update to investments page 2300 of GUI 301(shown in FIGS. 23-25) in response to selection of one or more strategyselection options 2706.

The update is configured to display additional information in glide path2314, which displays a graphical representation of asset allocation overtime as described above. More specifically, manual allocation strategy2918 graphically represents the user defined investment strategy, basedon captured asset strategy preference data, and is overlaid on optimizedallocation strategy 2316, which represents the optimal asset allocationstrategy over time, as described above. Thus, the update enables theuser to graphically compare the manually selected option 2706 to theoptimized allocation strategy 2316 calculated by planning engine 150. Inthe example embodiment, the update causes optimal allocation strategy2316 to appear as a dashed or muted line to indicate it is no longer theactive strategy.

The update also causes to be displayed a strategy alert 2920 oninvestments page 2300 in response to the user-selected investmentstrategy. In the example embodiment, GUI 301 causes to be displayedalert 2920 upon reception of a strategy selection option 2706 capturedfrom user 102. Specifically, when user 102 elects to manually choose astrategy selection option 2706, strategy alert 2920 is displayed.Strategy alert 2920 provides a link to re-access investment strategysettings, which may include re-transmitting constraints page 2600 (shownin FIG. 26), in the event that the user decides to under the manualstrategy selection

FIG. 30A depicts retirement summary page 3000 of GUI 301, which may beopened using income planning link 112 and displays projected replacementincome compared to a retirement goal. For example, user 102 may reviewthe projected income replacement generated by their currentcontributions and retirement savings, and evaluate the annual projectedretirement income.

Retirement summary page 3000 includes a current plan tab 3002 and a planmodel tab 3004. In FIG. 30A, current plan tab 3002 is selected anddisplays data based on current financial data such as salarycontributions, and asset allocations. Goal indicator 3008 is displayedin response to replacement income module 212 comparing the retirementgoal to the projected retirement income. In the example embodiment, theretirement income is not projected to meet the retirement goal, so goalindicator 3008 indicates as much.

A projected retirement income graph 3010 is generated by advisory rulesengine 202, using investment income module 206 and benefits module 210.Guaranteed income 3028 (e.g., annuities, social security,defined-benefit pensions) and variable income 3022 (e.g., investmentincome) are generated and displayed for each year of retirement in atwo-color bar graph. In some embodiments, retirement income graph 3010may further include retirement income goal 3024 and average projectedannual income 3026. In the example embodiment, income goal 3024 isgenerated based on replacement income module 212. For example, incomegoal 3024 may be projected based on a portion of salary income atretirement. Average projected annual income 3026 (e.g., achievableincome) defines an average expected investment income (e.g., averageyearly income throughout the life expectancy of the user, from anoptimal spend-down strategy based on the income factors of the user).

A current plan tab 3002 of retirement summary page 3000 also includesincome factor information 3012 for user 102 and, in some embodiments,the spouse/partner of user 102. Replacement income percentages 3014define a percentage of the projected salary at retirement needed forexpenses in retirement. In the example embodiment, 100% of the salariesof user 102 and user 102's spouse are projected to be needed inretirement. Benefit age 3018 defines a projected age when user 102 anduser 102's spouse begin receiving retirement benefits, such as a pensionor social security. Similarly, retirement age 3016 defines a desiredretirement age for user 102 and user 102's spouse. Additionally,estimated life expectancy 3020 defines a final year for which retirementincome will be needed, and a number of years where partial retirementincome may be needed, based on a reduced household.

Projected retirement income graph 3010 is configured such that user 102may select any year to view additional retirement income detail, such asthe benefit and/or investment income for each year. In the exampleembodiment shown in FIG. 30A, the age of the user (e.g., the primaryaccount holder) is displayed as the x-axis of projected retirementincome graph 3010. FIG. 30B illustrates another example projectedretirement income graph 3030 similar to graph 3010. In the exampleembodiment, the primary account holder has a spouse, and the spouses ageis illustrated as a second x-axis of the graph 3030, immediately belowthe age values of the user.

FIG. 31 depicts a current plan tab 3002 of retirement summary page 2000enlarged to show an income detail region 3100 in response to user 102selecting the individual bar of the graph corresponding to a retirementyear on retirement summary page 3000. For example, user 102 selects theyear of interest by hovering a pointer over the corresponding bar. User102 may review the investment income and/or benefit income projectiongenerated by planning engine 150 in a specific year of retirement. Forexample, the income from retirement plans and social security may changeover time. In the absence of a selection, the alphanumeric display inincome detail region 3100 is for a default year, such as the initialyear of retirement.

After user 102 selects a retirement year 3112 from projected retirementincome graph 3010, income detail region 3100 is generated by GUI 301.Income detail region 3100 includes year identifier 3104, variable income(e.g., investment income) 3126, guaranteed income 3128 (e.g., benefitincome), and projected year income 3122. In the example embodiment,projected 401(k) and social security income are aggregated to calculatea projected annual income at age 70. In the absence of a selection, theretirement year 3112 is set to a default year.

FIG. 32 depicts plan model tab 3004 selected on retirement summary page3000. A revisit my goals link 3208 allows user 102 to modify financialdata such as the retirement year, desired retirement age, and averagelife expectancy. In response to selection of revisit my goals link 3208,a revisiting goal page 3300 pops up, or overlays, retirement summarypage 3000, as discussed with respect to FIG. 33. In other words, revisitmy goals link 3208 allows user 102 to override calculated values withcustomized values for modeling purposes. Any overridden values aresubstituted for the corresponding income factor when modeling. Planmodel tab 3004 initially displays projected retirement income graph 3010based on current plan data. In response to the user inputting modellingvalues via revisit my goals link 202, planning engine 150 generates amodel projected retirement income graph 3410 based on the updatedfinancial data (e.g., retirement year, life expectancy), as shown inFIG. 34. Similarly, plan model tab 3004 initially displays income factorinformation 3012 as described above from current plan tab 3002, andplanning engine 150. In the example embodiment, again using the incomefactors from the database 120 but having the customized model projectedincome factor from FIG. 33 substituted for the corresponding databasefactor, the plan model tab 3004 also displays a model income goal line,similar to income goal 3024, and a model average projected annualincome, similar to average projected annual income 3026 (e.g.,achievable income). In the example embodiment, the database 120 is notupdated with the user's modeled values, unless the user takes additionalaffirmative action to modify the user's profile. Thus, the user is ableto graph various scenarios in the modelling tab 3004, and to toggle backto the actual current plan performance on current tab 3002 for easyvisual comparison against the same type of graph in the same displaylocation, without fear of accidentally changing the actual financialaccount settings.

FIG. 33 depicts revisiting goals page 3300, which facilitates user 102defining a model retirement goal for comparison purposes, by providingfinancial data such as model replacement income percentage 3308, modelretirement age, model social security age, and model life expectancy.User 102 selects what percentage of their current salary 3304 will beneeded in retirement using model income percentage 2208. The desiredmodel retirement age and model social security age may be adjusted usingsliders 3310 and 3312. For example, user 102 may desire to model theeffects of postponing retirement or an early retirement for comparisonpurposes. Model life expectancy may be adjusted for user 102 with slider3314. For example, user 102 may reduce their life expectancy to modelnew health concerns. In certain embodiments, user 102 may defineseparate model values for their spouse/partner using tab 3318. Morespecifically, tab 3318 may include the same fields described above, butassociated with the spouse of user 102. Update link 3316 is configuredto save the updated model financial data, and trigger planning engine150 to regenerate the model retirement income graph 3410 and modelprojected income factor information 3412 (shown in FIG. 34).

FIG. 34 depicts updated plan model tab 3004. In the example embodiment,updated plan model tab 3004 is generated in response to user 102providing updated model financial data, such as a model retirement ageand estimated life expectancy. Modeled retirement income graph 3410 isregenerated by planning engine 150. In the example embodiment, formodelling purposes, user 102 reduced their retirement income percentageto 75%, indicating they would need only 75% of their current salary.Updated plan model tab 3004 includes the updated model income factors3412, including the replacement income percentage 3414, and modelretirement income graph 3410 displays the adjusted retirement goal 3424.

User 102 may also customize the market prediction used to generatevalues on retirement summary page 3000. For example, user 102 may expectabove or below average market growth. Market performance selector 3006is configured to cause planning engine 150 to regenerate retirementincome graph 3410 based on the customized market performance predictionselected by the user. More specifically, market performance selector3006 may adjust the return rates used by return calculation module 204.For example, user 102 may select poor market performance from marketperformance selector 3006 to evaluate their ability to retire in poormarket conditions. As another example, user 102 may select excellentmarket performance from market performance selector 3006 to determine ifabove-average market performance would allow them to meet theirretirement goals.

In some embodiments, retirement summary page 3000 including both currentplan tab 3002 and plan model tab 3004, with identical formats forprojected retirement income graph 3010 and model retirement income graph3410 and identical formats for income factor information 3012 andprojected model income factor information 3412, facilitates GUI 301providing improved functionality for each of comparison of multiplealternate account options to current account settings across a range ofpotential market conditions.

FIG. 35 depicts an exemplary savings rate page 3500 of GUI 301, whichmay be opened using savings link 1106, and facilitates user input ofaccount data, such as a desired contribution rate, and displays aplurality of contribution rate levels. In the exemplary embodiment,savings rate page 3500 includes a contribution scale 3504 which includesa plurality of contribution rate levels such as a current contributionrate 3506, a company match rate 3508, a recommended contribution rate3510, and an IRS limit rate 3512. Contribution scale 3504 is a componentof a widget which also includes contribution slider 3502. Contributionslider 3502 facilitates interactive input of a desired contribution rateby user 102. Specifically, a user is able to change the location ofcontribution slider 3502 along contribution scale 3504, wherein a givencontribution rate is determined by the position of contribution slider3502 along contribution scale 3504. Contribution slider 3502 is alsoconfigured to display a numeric value (e.g., 4%) corresponding to thecontribution rate determined by contribution slider 3502. FIG. 36illustrates slider 3502 moved to a new location 3602, which, in theexample embodiment, increases the contribution rate to 5%.

The plurality of contribution rate levels are dynamically generated andtransmitted by planning engine 150 based on the user profile data indatabase 120. In some embodiments, contributions module 208 (shown inFIG. 1B) generates and transmits the plurality of contribution ratelevels. In some embodiments, planning engine 150 and/or contributionsmodule 208 retrieve financial data from a database such as database 120(shown in FIG. 1A) and use the financial data to generate at least oneof the plurality of contribution rate levels. Current contribution rate3506 is based on contribution data collected from user 102 or from theemployer as a financial data source 116. Company match rate 3508 isbased on contribution and or benefits data collected from user 102.Recommended contribution rate 3510 is generated by planning engine 150,in some cases by contributions module 208, based on user profile dataand account data, such as age, salary, asset data, and financial goals.IRS limit rate 3512 is based on user profile data, account data, andfinancial data retrieved from database 120 or financial data source 116(shown in FIG. 1A).

Savings rate page 3500 is also configured to display an opportunitiesalert 3514, which is generated by planning engine 150 based on userprofile data and account data, such as financial goals and contributiondata. In some embodiments, opportunities alert 3514 is generated bycontributions module 208. Savings rate page 3500 is also configured tofacilitate the transmission of a desired contribution rate throughcontinuation request 3516. Continuation request 3516 is also configuredto facilitate user access to another webpage, such as savings type page3700 (shown in FIG. 37). Alternatively, the changes on savings rate page3500 may be discarded using back request 3518.

FIG. 37 depicts an exemplary savings type page 3700 of GUI 2001, whichmay open automatically in response to selecting a savings contributionusing savings rate page 3500. In the example embodiment, savings typepage 3700 facilitates user selection of the type of account(s) (e.g.,savings type) to which the user's savings contributions will be divided.The options include a recommended contribution type 3702, which isgenerated and transmitted by planning engine 150 based on user profiledata, account data, and financial data, such as age, financial goals,assets, and contribution data. For example, based on user 102's age,financial goals, and desired contribution rate, planning engine 150 maydetermine that an entire desired contribution rate (e.g., savings rate)of 5% should be contributed to a Roth IRA. In some embodiments,contributions module 208 (shown in FIG. 1B) generates the recommendedcontribution account type. The options also include a manualcontribution type 3704, which facilitates the manual selection by user102 of specific account types for the savings contribution.

FIG. 38 depicts savings type page 3700 enlarged to include an exemplarymanual selector region 3800 in response to selection of manualcontribution type 3704. In the example embodiment, manual selectionregion 3800 facilitates the manual selection of specific account typesfor the user's savings contribution. More specifically, manual selectionregion 3800 is configured to display a plurality of account types, suchas account types 3806, 3808, and 3810. For example, account type 3806may represent a “Before Tax” account, account type 3808 may represent a“Roth” account, and account type 3810 may represent a “Catch Up”account. Manual selection region 3800 is also configured to displaycontribution sliders 3812, 3814, and 3816 to facilitate receivingcontribution rates from user 102 for the respective account types.

Savings type page 3700 is also configured to facilitate the transmissionof contribution preferences and selected contribution account typesthrough continuation request 3706. Continuation request 3706 is furtherconfigured to facilitate access to another webpage, such as contributionreview page 3900. Alternatively, back button 3708 may be selected todiscard changes.

FIG. 39 depicts an exemplary contribution review page 3900 of GUI 301,which displays a summary of changes made to a user's 102 contributionpreferences via pages 3500 and 3700 and receives user input confirmingthe changes from a submit changes button 3906.

Contribution review page 3900 is configured to display a requestedchange summary 3902, which contains indications for previouscontribution preferences and updated contribution preferences, based onchanges made by user 102. Contribution review page 3900 is furtherconfigured to display change detail 3904. Change detail 3904 includesinformation detailing the updated contribution preferences which will beapplied to a given account.

Contribution review page 3900 is also configured to facilitate access toanother webpage, such as contribution confirmation page 4000, throughsubmit changes button 3906. Alternatively, the changes may be discardedusing cancel button 3908.

FIG. 40 depicts an exemplary contribution confirmation page 4000 of GUI301, which displays a confirmation notice of changes made to a user's102 contribution preferences in response to selection of submit changesbutton 3906.

Contribution confirmation page 4000 is configured to display confirmedchange 4002, which contains indications for previous contributionpreferences and updated contribution preferences, based on changes madeby user 102. Contribution confirmation page 4000 is further configuredto display confirmation summary 4004. In the exemplary embodiment,confirmation summary 4004 includes a confirmation number and an accountwhich is affected by the changes to contribution preferences.

Contribution confirmation page 4000 is also configured to facilitateaccess to another webpage, such as savings goal page 4100, throughcontinue request 4006.

FIG. 41 depicts an exemplary savings goal page 4100 of GUI 301, whichmay be opened using retirement goal link 1102, and which displaysfinancial information related to a user 102's financial goals. In theexemplary embodiment, savings goal page displays financial informationrelated to user 102's retirement goals and facilitates the input of userprofile data and account data, such as financial goals and retirementage.

Savings goal page 4100 is configured to display user goal 4102 andspouse goal 4112. User goal 4102 and spouse goal 4112 are generated byplanning engine 150 based on user profile data and account data such ascurrent income, such as user current income 4104 and spouse currentincome 4114, and retirement income goals, such as desired userretirement income amount 4108 and desired spouse retirement incomeamount 4118. In the exemplary embodiment, based on current incomes 4104and 4114 and desired retirement income amounts 4108 and 4118, planningengine 150 calculates a monthly retirement income, displayed as usergoal 4102 and spouse goal 4112. Savings goal page 4100 is alsoconfigured to accept user input defining retirement income format forthe user and spouse via format inputs 4106 and 4116. In the exampleembodiment, format inputs 4106 and 4116 are set to “%”, such that thedesired retirement income amounts 4108 and 4118 are entered as apercentage of respective current incomes 4104 and 4114. In analternative embodiment, format inputs 4106 and 4116 are set to “$”, suchthat the desired retirement income amounts 4108 and 4118 are entered asan absolute dollar amount. Savings goal page 4100 is also configured todisplay a household income goal 4122, based on user goal 4102 and spousegoal 4112.

Savings goal page 4100 is configured to facilitate the transmission ofupdated savings goals by accepting user changes using an through updaterequest 4124. Update request 4124 is also configured to facilitateaccess to another webpage, such as retirement dashboard 1100 (shown inFIG. 11). Alternatively, changes may be discarded using back button4126.

In some embodiments, the financial planning system provides onlineadvice services to users. Users may register for online advice throughan enrollment page (not shown) (e.g., via online advice link 812 of FIG.8A), or may otherwise access the online advice through the “Help Me DoIt” link 304 on introductory page 300 (shown in FIG. 3). The user mayenter or edit profile data via the about me page 1200 (shown in FIG.12).

FIG. 42 depicts an alternative exemplary embodiment of savings rate page3500, here designated savings rate page 4200. In some embodiments,savings rate page 4200, rather than savings rate page 3500 (shown inFIG. 35), is caused to be displayed by selection of savings link 1106(shown on the dashboard 1100 of FIG. 11) or by selection of a jump linkin opportunities area 1126. Savings rate page 4200 presents a series ofsavings rate and savings type (e.g., tax-deferred or non-tax-deferredcontributions to a 401(k) plan) options similar to savings rate page3500, but in an alternative user-friendly format.

In some embodiments, GUI computer system 114 identifies a 401(k) plan ofthe user and analyzes the plan data against the user's current profilein database 120 to identify any of four savings options 4202 that may beapplicable for the user: (A) maintaining a current contribution rate;(B) maintaining a current savings rate but changing a current savingstype (i.e., change investment type) (e.g., to Roth IRA), (C) maintaininga current savings type but changing a current savings rate to equal acompany match rate (e.g., increase the current savings rate to“maximize” the user's benefit from the company match policy if the useris currently not taking advantage of company match rate), or (D)changing the current savings rate to reach a user goal. The GUI computersystem 114 dynamically determines which of these options are relevant tothe user, and causes to be displayed on savings rate page 4200 (or,alternatively, savings rate page 3500) the relevant savings options asoptions from which the user may select. For example, if the user'scurrent savings type (i.e., pre-tax versus Roth contributions) isalready optimal for the user's situation, the “change investment type”option is not displayed. For another example, if the user's contributionrate already meets or exceeds the company match rate, the “maximizecompany match” option is not displayed. For another example, if theuser's contribution rate and type already enable the user's projectedincome in retirement to meet the user's goal, the “reach my goal” optionis not displayed. The option for the user to manually enter auser-selected savings rate and type is also provided, and is presentedas the final option in the dynamically generated list. The savingsfunctionality allows participants to view their current savings strategyand view savings recommendations for all accounts that are enrolled inenhanced services.

One problem with conventional recommendation systems is the generationof too many recommendations that overwhelm the user, recommendationsthat are too complex for the user to grasp, or recommendations thatresult in changes that appear extreme to the user. The dynamicgeneration and display of relevant savings options on savings rate page4200 provides the user with incremental, easily understood options forimproving the user's income in retirement.

As discussed above with respect to dashboard 1100, in some embodiments,GUI computer system 114 includes an opportunity rules engine configuredto analyze the profile data of the user and identify recommendations forthe user based on the user profile data, and without calling the atleast one planning engine 150 to directly evaluate the candidatemodifications. In some embodiments, the opportunity rules engineoperates on a predetermined ordered list of candidate modifications thathave been proved to be incremental, easily accepted ways to improveusers' ability to meet retirement goals. The opportunity rules engine isprogrammed to identify, based on the respective user profile and withoutcalling the at least one planning engine 150 to directly evaluate thecandidate modifications, one of the candidate modifications that is notconsidered to be an “extreme” change from the value currently in theuser profile and is likely to benefit the user, and to display inopportunity area 1126 a message recommending the identified candidatemodification, and an associated jump link to a page of GUI 301 enablingthe respective user to execute the identified candidate modification. Insome embodiments, by identifying and displaying only a single,incremental modification, GUI 301 increases a likelihood the that theuser will consider and adopt the recommendation. Additionally oralternatively, by providing a jump-link directly to a page of GUI 301that enables the user to execute the recommendation, GUI 301 furtherincreases a likelihood the that the user will adopt the recommendation.

Examples that may be included in the ordered list of candidatemodifications include changes to the savings rate and savings type ofthe user's contributions to the financial account (which may includeoptions similar to the dynamically generated options listed above), aswell as addition of profile data for fields which the user has not yetentered data (e.g., replacing null values for the user in the “otherassets” or “family information” fields of database 120). It should benoted that whether or not the user is currently reaching the user's goalis known from an initial call to planning engine 150 to obtain thenumbers needed for estimated income widget 1130, but the other potentialcandidate modifications to savings rate and type are evaluated by theopportunities rules engine without calling planning engine 150. Theopportunity rules engine may identify the candidate from the orderedlist by selecting a first candidate modification in the ordered list anddetermining whether the selected candidate modification has beenimplemented in the user profile. If the selected candidate modificationhas been implemented, the opportunity rules engine skips that candidatemodification and selects the next candidate modification from theordered list. In some embodiments, if the selected candidatemodification has not been implemented, the opportunity rules engineidentifies the candidate modification for display in the opportunityarea 1126. In other embodiments, if the selected candidate modificationhas not been implemented, the opportunity rules engine compares thecandidate modification to a current value of at least one associateddata field in the user profile, and evaluates (e.g., based on a look-uptable in database 120) whether the candidate modification would beclassified as an “extreme” change relative to the current value. If thecandidate modification is not extreme, the opportunity rules engineidentifies the selected candidate modification for display. If thecandidate modification is determined to qualify as “extreme,” theopportunity rules engine skips that candidate modification, selects thenext candidate modification from the ordered list, and repeats theprocess.

For example, in the context of savings advice page 4200, the opportunityrules engine is configured to analyze the profile data of the user andidentify one of the savings options as a savings recommendation 4210.The list of savings options may sorted into an ordered list of candidatemodifications for the user based on the user profile data and withoutcalling the planning engine 150. In the example embodiment, the savingsrecommendation 4210 is further identified on the savings advice page4200 with a “RECOMMENDED” flag. In some embodiments, the savingsrecommendation 4210 may be presented on the dashboard 1100 inopportunity area 1126. When the user selects the opportunity area 1126from the dashboard 1100, or in some cases a highlighted portion of themessage displayed in opportunity area 1126, the opportunity area 1126acts as a jump link, causing the savings advice page 4200 to bedisplayed to the user along with the savings recommendation 4210 flaggedas shown in FIG. 42.

As discussed above, in some embodiments, the user profile includesfamily information fields for the user (e.g., spousal data, dependentsdata) and the ordered list of candidate modifications includes replacingnull values for the respective user in the family information field.Further, the opportunity rules engine may provide a jump link associatedwith the candidate modification that allows the user to bypass the userprofile summary page and go directly to the family information fields toreplace the family information fields.

In some embodiments, the ordered list of candidate modificationsincludes a sequence of candidate savings modifications includingmaintaining a current savings rate and changing a savings type, changingthe current savings rate to equal a company match rate, and changing thecurrent savings rate to meet the user goal. Each candidate modificationmay include a jump link that links to savings rate page 3500, allowingthe user to change the savings rate directly. The savings rate page 3500may include the opportunity area, wherein after activation of the jumplink, the message is propagated to the opportunity area of the savingsrate page 3500.

In some embodiments, the opportunity link 1114 causes the opportunityrules engine to execute an opportunities flow process. FIG. 57 depictsan exemplary opportunities page 5700 that allows the user to stepthrough an ordered list of opportunities identified by the opportunityrule engine. The opportunities page 5700 displays one of the identifiedopportunities of the list within the opportunities area 1126 andprovides a back link 5714 and a next opportunity link 5712 that allowsthe user to step through the sequence. In the exemplary embodiment, theopportunities flow includes the following steps in sequence: (i)selecting the first candidate modification in the ordered list; (ii)determining whether the selected candidate modification has beenimplemented in the user profile; (iii) if the selected candidatemodification has been implemented, selecting the next candidatemodification from the ordered list and returning to step (ii); (iv) ifthe selected candidate modification has not been implemented, displaying(a) the message recommending the identified candidate modification(e.g., in opportunities area 1126), (b) the associated jump link (e.g.,“Learn more”, as shown in FIG. 57), and (c) a next-opportunity link5712; (v) in response to activation of the next-opportunity link 5712,selecting the next candidate modification from the ordered list andreturning to step (ii); and (vi) in response to activation of the jumplink, exiting the opportunities flow process.

In some embodiments, the planning engine 150 determines a projectedretirement income based on a savings rate and an assumed savings typebeing tax-deferred. The planning engine 150 may re-determine theprojected retirement income based on the savings rate and anon-tax-deferred savings type. The GUI 301 may include in the list ofsavings options 4202 a “change type” selector enabling the user tomaintain the savings rate value and update the savings type totax-deferred or non-tax-deferred in response to the savings type beingthe other of tax-deferred and non-tax-deferred. The planning engine 150may further determine a goal-based savings rate and a goal-based savingstype, where the goal-based savings rate and the goal-based savings typeare determined based on a minimum savings rate that enables therespective user to meet the user's goal.

In some embodiments, the GUI 301 may include in the list of savingsoptions 4202 a goal-based selector enabling the user to update thesavings rate to a goal-based savings rate and the savings type to thegoal-based savings type. In some embodiments, the GUI may compare thesavings rate to a maximum company-match value associated with thefinancial plan and, in response to determining that the savings rate isless than the company-match value, include a company-match selectorenabling the user to update the savings rate to the maximumcompany-match value. In some embodiments, the GUI 301 may include auser-choice selector in the list of savings options 4202 that enablesthe user to input a new value for the savings rate. In some embodiments,in response to receiving the updated savings rate, the planning engine150 determines a projected updated retirement income based on theupdated savings rate and the assumed savings type being non-tax-deferredand re-determines the projected updated retirement income based on thenew savings rate and the assumed savings type being non-tax-deferred. Inresponse to the savings type being one of tax-deferred ornon-tax-deferred and the projected updated retirement income beinghigher for the assumed savings type being the other of tax-deferred andnon-tax-deferred, the GUI 301 displays to the user a recommendation toupdate the savings type field to the other of the tax-deferred andnon-tax-deferred type. In some embodiments, displaying the list ofsavings options 4202 (and associated selectors) includes displaying thesavings options 4202 in a hierarchical order corresponding to a degreeof change of the savings rate, and wherein the company-match selectorappears after the change-type selector, the goal-based selector appearsafter the company-match selector, and the user-choice selector appearsafter the goal-based selector. In some embodiments, the savings options4202 include a no-change selector that allows the user to maintain thecurrent savings rate and savings type. The no-change selector may appearbefore the change-type selector. In some embodiments, displaying thelist of savings options 4202 includes displaying the goal-based selectoras a default selection. In some embodiments, the GUI 301 displays areview screen in response to the user selecting one of the savingsoptions 4202. The review screen may include a submit-changes linkoperable to execute the selected updates in the user profile and acancel-changes link operable to maintain the savings rate and savingstype.

FIG. 43 depicts an exemplary investment advice page 4300 that may beprovide as a part of the online advice services to the user. Once theuser has completed the savings advice page 4200, either by selecting anew option or continuing with their existing savings rate, the user isnext presented with the investment advice page 4300. The investmentadvice page 4300, in the example embodiment, analyzes the user profiledata to generate investment recommendations for 4312. The investmentadvice page 4300 includes a current investment section 4310 illustratingfunds in which the user is currently invested, as well as a currentinvestment risk level (e.g., “moderate conservative”). The investmentadvice page 4300 also includes an investment recommendations section4312 that illustrates a recommended risk level (e.g., a change to“moderate”) as well as a list of recommended investments 4314 andrecommended allocations 4316 (e.g., shown here as percentages). In someembodiments, the recommended allocations 4316 are provided by theplanning engine 150 or a third-party service similar to the planningengine 150 configured to analyze user profile data and generate suchrecommendations.

FIG. 44 depicts an exemplary change review page 4400. If the userchooses to continue with the recommended allocations 4316, theopportunity rules engine displays the change review page 4400 to theuser. The change review page 4400, in the example embodiment, includes asavings change summary 4410 and an investment change summary 4412 forreview by the user. The savings change summary 4410 displays any changeto savings selected by the user on the savings advice page 4200. Theinvestment change summary 4412 displays any change to investmentsselected by the user on the investment advice page 4300.

FIG. 45 depicts an exemplary confirmation page 4500. After the usersubmits the changes from the change review page 4400, the opportunityrules engine submits the portfolio changes and displays confirmationinformation 4510 to the user for summary and record keeping purposes.

FIG. 46 depicts an exemplary social security page 4600 that allows theuser to identify at what age they intend to begin taking Social Securitybenefit.

FIG. 47 depicts an exemplary social security benefits page 4700 thatillustrates social security benefits calculations for the user based onretirement age.

FIG. 48 depicts an exemplary institution selection page 4800 that allowsthe user to identify a third-party institution which may manage otherinvestments of the user, and for which auto-linking of the user'sthird-party account information is available.

FIG. 49 depicts an exemplary account link page 4900 that allows the userto identify information about a linked account identified via theinstitution selection page 4800.

FIG. 50 depicts an exemplary retirement asset page 5000 that allows theuser to add a retirement asset to their portfolio.

FIGS. 51A and 51B depict exemplary asset configuration pages 5100, 5110that allows the user to configure assets.

FIGS. 52A and 52B depict exemplary account configuration pages 5200,5210 that allows the user to configure accounts.

FIGS. 53A and 53B depict exemplary account configuration pages 5300,5310 that allows the user to configure accounts.

FIG. 54 is an exemplary assets page 5400 that allows the user to add andview their accounts.

FIG. 55 is an exemplary savings goals page 5500 that allows the user toadd savings goals.

FIG. 56 is another exemplary add retirement asset page 5600 in “pop up”form that allows the user to add a retirement asset.

FIG. 57 is an exemplary opportunities page 5700 that allows the user toview and step through opportunities, as discussed above.

As will be appreciated based on the foregoing specification, theabove-described embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof,wherein the technical effect is to provide virtualization and fraudsecurity around fundraising and redemption in an online paymenttransaction environment. Any such resulting program, havingcomputer-readable code means, may be embodied or provided within one ormore computer-readable media, thereby making a computer program product,(i.e., an article of manufacture), according to the discussedembodiments of the disclosure. The computer-readable media may be, forexample, but is not limited to, a fixed (hard) drive, diskette, opticaldisk, magnetic tape, semiconductor memory such as read-only memory(ROM), and/or any transmitting/receiving medium such as the Internet orother communication network or link. The article of manufacturecontaining the computer code may be made and/or used by executing thecode directly from one medium, by copying the code from one medium toanother medium, or by transmitting the code over a network.

These computer programs (also known as programs, software, softwareapplications, “apps”, or code) include machine instructions for aprogrammable processor, and can be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” “computer-readable medium” refers to any computer programproduct, apparatus and/or device (e.g., magnetic discs, optical disks,memory, Programmable Logic Devices (PLDs)) used to provide machineinstructions and/or data to a programmable processor, including amachine-readable medium that receives machine instructions as amachine-readable signal. The “machine-readable medium” and“computer-readable medium,” however, do not include transitory signals.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

This written description uses examples to disclose the disclosure,including the best mode, and also to enable any person skilled in theart to practice the disclosure, including making and using any devicesor systems and performing any incorporated methods. The patentable scopeof the disclosure is defined by the claims, and may include otherexamples that occur to those skilled in the art. Such other examples areintended to be within the scope of the claims if they have structuralelements that do not differ from the literal language of the claims, orif they include equivalent structural elements with insubstantialdifferences from the literal language of the claims.

What is claimed is:
 1. A graphical user interface (GUI) for a financialplanning system, the financial planning system including at least oneplanning engine in communication with a database, the database storinguser profiles for a plurality of users, each user registered forservices with respect to a financial account of the respective user,each of the user profiles including first values for a user goal field,a savings-rate field, and a savings-type field for the respective user,the GUI comprising a savings rate page programmed to generate anddisplay a list of savings-option selectors by: determining, using the atleast one planning engine, a projected retirement income based on afirst value of the savings-rate field and an assumed savings type beingtax-deferred; re-determining, using the at least one planning engine,the projected retirement income based on the first value of thesavings-rate field and the assumed savings type being non-tax-deferred;in response to (i) the first value of the savings-type field being oneof tax-deferred and non-tax-deferred, and (ii) the projected retirementincome being higher for the assumed savings type being the other oftax-deferred and non-tax-deferred, including in the list ofsavings-option selectors a change-type selector enabling the respectiveuser to (i) maintain the first value of the savings-rate field and (ii)update the savings-type field to the other of tax-deferred andnon-tax-deferred; determining, using the at least one planning enginebased on the user profile, a goal-based savings rate and a goal-basedsavings type, wherein the goal-based savings rate and the goal-basedsavings type are determined based on a minimum savings rate that enablesthe respective user to meet the first value of the user goal field; inresponse to at least one of (i) the goal-based savings rate differingfrom the first value of the savings-rate field, and (ii) the goal-basedsavings type differing from the first value of the savings-type field,including in the list of savings-option selectors a goal-based selectorenabling the respective user to update (i) the savings-rate field to thegoal-based savings rate and (ii) the savings-type field to thegoal-based savings type; and displaying the list of savings-optionselectors.
 2. The GUI according to claim 1 further comprising: comparingthe first value of the savings-rate field to a maximum company-matchvalue associated with a financial plan; and in response to determiningthat the first value of the savings-rate field is less than thecompany-match value, including in the list of savings-option selectors acompany-match selector enabling the respective user to update thesavings-rate field to the maximum company-match value.
 3. The GUIaccording to claim 2 further comprising: including in the list ofsavings-option selectors a user-choice selector enabling the respectiveuser to input a user-input value for the savings-rate field; andupdating the savings-rate field to the user-input value.
 4. The GUIaccording to claim 3 further comprising, in response to receiving theuser-input value from the respective user: determining, using the atleast one planning engine, a projected updated retirement income basedon the user-input value of the savings-rate field and an assumed savingstype being tax-deferred; re-determining, using the at least one planningengine, the projected updated retirement income based on the user-inputvalue of the savings-rate field and the assumed savings type beingnon-tax-deferred; in response to (i) the first value of the savings-typefield being one of tax-deferred and non-tax-deferred, and (ii) theprojected updated retirement income being higher for the assumed savingstype being the other of tax-deferred and non-tax-deferred, displaying tothe respective user a recommendation to update the savings-type field tothe other of tax-deferred and non-tax-deferred.
 5. The GUI according toclaim 3, wherein displaying the list of savings-option selectors furthercomprises displaying the savings-option selectors in a hierarchicalorder corresponding to a degree of change of the savings-rate field fromthe first value of the savings-rate field, wherein: the company-matchselector appears after the change-type selector; the goal-based selectorappears after the company-match selector; and the user-choice selectorappears after the goal-based selector.
 6. The GUI according to claim 5further comprising including in the list of savings-option selectors ano-change selector operable to maintain the first values for both thesavings-rate and savings-type fields, wherein the hierarchical orderfurther includes the no-change selector appearing before the change-typeselector.
 7. The GUI according to claim 1, wherein displaying the listof savings-option selectors further comprises displaying the goal-basedselector as a default selection.
 8. The GUI according to claim 1 furthercomprising, in response to the respective user selecting one of thesavings-option selectors, displaying a review screen comprising: asubmit-changes link operable to execute the associated updates in theuser profile; and a cancel link operable to maintain the first values ofthe savings-rate field and the savings-type field.
 9. Acomputer-implemented method for implementing a graphical user interface(GUI) for a financial planning system, the financial planning systemincluding at least one planning engine in communication with a database,the database storing user profiles for a plurality of users, each userregistered for services with respect to a financial account of therespective user, each of the user profiles including first values for auser goal field, a savings-rate field, and a savings-type field for therespective user, the method comprising: determining, using the at leastone planning engine, a projected retirement income based on a firstvalue of the savings-rate field and an assumed savings type beingtax-deferred; re-determining, using the at least one planning engine,the projected retirement income based on the first value of thesavings-rate field and the assumed savings type being non-tax-deferred;in response to (i) the first value of the savings-type field being oneof tax-deferred and non-tax-deferred, and (ii) the projected retirementincome being higher for the assumed savings type being the other oftax-deferred and non-tax-deferred, including in a list of savings-optionselectors a change-type selector enabling the respective user to (i)maintain the first value of the savings-rate field and (ii) update thesavings-type field to the other of tax-deferred and non-tax-deferred;determining, using the at least one planning engine based on the userprofile, a goal-based savings rate and a goal-based savings type,wherein the goal-based savings rate and the goal-based savings type aredetermined based on a minimum savings rate that enables the respectiveuser to meet the first value of the user goal field; in response to atleast one of (i) the goal-based savings rate differing from the firstvalue of the savings-rate field, and (ii) the goal-based savings typediffering from the first value of the savings-type field, including inthe list of savings-option selectors a goal-based selector enabling therespective user to update (i) the savings-rate field to the goal-basedsavings rate and (ii) the savings-type field to the goal-based savingstype; and displaying the list of savings-option selectors on a savingsrate page of the GUI.
 10. The computer-implemented method of claim 9further comprising: comparing the first value of the savings-rate fieldto a maximum company-match value associated with a financial plan; andin response to determining that the first value of the savings-ratefield is less than the company-match value, including in the list ofsavings-option selectors a company-match selector enabling therespective user to update the savings-rate field to the maximumcompany-match value.
 11. The computer-implemented method of claim 10further comprising: including in the list of savings-option selectors auser-choice selector enabling the respective user to input a user-inputvalue for the savings-rate field; and updating the savings-rate field tothe user-input value.
 12. The computer-implemented method of claim 11further comprising: determining, using the at least one planning engine,a projected updated retirement income based on the user-input value ofthe savings-rate field and an assumed savings type being tax-deferred;re-determining, using the at least one planning engine, the projectedupdated retirement income based on the user-input value of thesavings-rate field and the assumed savings type being non-tax-deferred;in response to (i) the first value of the savings-type field being oneof tax-deferred and non-tax-deferred, and (ii) the projected updatedretirement income being higher for the assumed savings type being theother of tax-deferred and non-tax-deferred, displaying to the respectiveuser a recommendation to update the savings-type field to the other oftax-deferred and non-tax-deferred.
 13. The computer-implemented methodof claim 11, wherein displaying the list of savings-option selectorsfurther comprises displaying the savings-option selectors in ahierarchical order corresponding to a degree of change of thesavings-rate field from the first value of the savings-rate field,wherein: the company-match selector appears after the change-typeselector; the goal-based selector appears after the company-matchselector; and the user-choice selector appears after the goal-basedselector.
 14. The computer-implemented method of claim 13 furthercomprising including in the list of savings-option selectors a no-changeselector operable to maintain the first values for both the savings-rateand savings-type fields, wherein the hierarchical order further includesthe no-change selector appearing before the change-type selector. 15.The computer-implemented method of claim 9, wherein displaying the listof savings-option selectors further comprises displaying the goal-basedselector as a default selection.
 16. The computer-implemented method ofclaim 9 further comprising, in response to the respective user selectingone of the savings-option selectors, displaying a review screencomprising: a submit-changes link operable to execute the associatedupdates in the user profile; and a cancel link operable to maintain thefirst values of the savings-rate field and the savings-type field. 17.At least one non-transitory computer-readable storage media thatincludes computer-executable instructions for implementing a graphicaluser interface (GUI) for a financial planning system, the financialplanning system including at least one planning engine in communicationwith a database, the database storing user profiles for a plurality ofusers, each user registered for services with respect to a financialaccount of the respective user, each of the user profiles includingfirst values for a user goal field, a savings-rate field, and asavings-type field for the respective user, the GUI generated by atleast one processor, wherein when executed by the at least oneprocessor, the computer-executable instructions cause the at least oneprocessor to: determine, using the at least one planning engine, aprojected retirement income based on a first value of the savings-ratefield and an assumed savings type being tax-deferred; re-determine,using the at least one planning engine, the projected retirement incomebased on the first value of the savings-rate field and the assumedsavings type being non-tax-deferred; in response to (i) the first valueof the savings-type field being one of tax-deferred andnon-tax-deferred, and (ii) the projected retirement income being higherfor the assumed savings type being the other of tax-deferred andnon-tax-deferred, include in a list of savings-option selectors achange-type selector enabling the respective user to (i) maintain thefirst value of the savings-rate field and (ii) update the savings-typefield to the other of tax-deferred and non-tax-deferred; determine,using the at least one planning engine based on the user profile, agoal-based savings rate and a goal-based savings type, wherein thegoal-based savings rate and the goal-based savings type are determinedbased on a minimum savings rate that enables the respective user to meetthe first value of the user goal field; in response to at least one of(i) the goal-based savings rate differing from the first value of thesavings-rate field, and (ii) the goal-based savings type differing fromthe first value of the savings-type field, include in the list ofsavings-option selectors a goal-based selector enabling the respectiveuser to update (i) the savings-rate field to the goal-based savings rateand (ii) the savings-type field to the goal-based savings type; anddisplay the list of savings-option selectors on a savings rate page ofthe GUI.
 18. The at least one non-transitory computer-readable storagemedia of claim 17, wherein the computer-executable instructions causethe at least one processor to: compare the first value of thesavings-rate field to a maximum company-match value associated with afinancial plan; and in response to determining that the first value ofthe savings-rate field is less than the company-match value, include inthe list of savings-option selectors a company-match selector enablingthe respective user to update the savings-rate field to the maximumcompany-match value.
 19. The at least one non-transitorycomputer-readable storage media of claim 18, wherein thecomputer-executable instructions cause the at least one processor to:include in the list of savings-option selectors a user-choice selectorenabling the respective user to input a user-input value for thesavings-rate field; and update the savings-rate field to the user-inputvalue.
 20. The at least one non-transitory computer-readable storagemedia of claim 18, wherein the computer-executable instructions causethe at least one processor to, in response to the respective userselecting one of the savings-option selectors, display a review screencomprising: a submit-changes link operable to execute the associatedupdates in the user profile; and a cancel link operable to maintain thefirst values of the savings-rate field and the savings-type field.